Allow `pipeline:expedite` to be set without `master:broken`, `master:foss-broken` or `quarantine`

Problem to solve

After a Slack discussion, it's clear that pipeline:expedite can be used for different use-cases:

  • broken master
  • fixing a regression quickly
  • quarantining a flaky test

Currently, you can only add pipeline:expedite if you've also set master:broken, master:foss-broken or quarantine.

Note: Danger also fails if you set pipeline:expedite on an MR that targets a stable branch.

Latest proposal

Allow pipeline:expedite to be set without master:broken, master:foss-broken or quarantine. Regularly monitor that pipeline:expedite isn't used for un-justified use-cases.

Old proposal

I'm proposing to remove these restrictions in favor of posting a thread upon addition of pipeline:expedite with the following question:

Please detail the reason why ~"pipeline:expedite" is needed for this merge request.

That way we trust our engineers by default but keep an "audit trail" if any breakage is introduced due to the pipeline:expedite label.

Edited by Rémy Coutable