-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Open
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.sig/docsCategorizes an issue or PR as relevant to SIG Docs.Categorizes an issue or PR as relevant to SIG Docs.sig/testingCategorizes an issue or PR as relevant to SIG Testing.Categorizes an issue or PR as relevant to SIG Testing.
Description
What would you like to be added:
If there is a Netlify preview for k/website or k/contributor-site, and an org member uses the /retest command, trigger Netlify to rebuild it.
Why is this needed:
There is currently no nice way for a contributor to self-service request a new Netlify test if there has been a flake or similar failure. The author (and only the author) can push an amended commit, but this is a lot of technical work for a simple step.
Metadata
Metadata
Assignees
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.sig/docsCategorizes an issue or PR as relevant to SIG Docs.Categorizes an issue or PR as relevant to SIG Docs.sig/testingCategorizes an issue or PR as relevant to SIG Testing.Categorizes an issue or PR as relevant to SIG Testing.