Skip to content

Rename ~pipeline:expedite-master-fixing label to ~pipeline:expedite

David Dieulivol requested to merge ddieulivol-rename_expedite_master_fixing_label_to_expedite into master

What does this MR do and why?

Relates to gitlab-org/gitlab#385738 (closed), which is step 1 of gitlab-org/ruby/gems/gitlab-dangerfiles#28 (comment 1209372811).

Follow-up of gitlab-org/ruby/gems/gitlab-dangerfiles!135 (comment 1209117246)

Renaming ~"pipeline:expedite-master-fixing" to pipeline:expedite

From Draft to Ready

Expected impact & dry-runs

None, as long as gitlab-org/gitlab!106971 (merged) is merged around the same time as this MR.

Action items

  • (If applicable) Add documentation to the handbook pages for Triage Operations =>
  • (If applicable) Identify the affected groups and how to communicate to them:
    • /cc @person_or_group =>
    • Relevant Slack channels => #development, #quality, #eng-managers, #frontend_maintainers, #backend_maintainers
:mega: The label ~pipeline:expedite-master-fixing will be renamed to ~pipeline:expedite in order to use it in more use-cases than broken master (see https://gitlab.com/gitlab-org/gitlab/-/issues/385738). The CI/CD pipelines, triage-ops and the documentation will be updated accordingly.
  • Engineering week-in-review
Edited by Rémy Coutable

Merge request reports