Disable `RemindMergedMrDeviatingFromGuideline` for release prep MRs
requested to merge disable-RemindMergedMrDeviatingFromGuideline-for-mrs-targeting-stable-branches into master
What does this MR do and why?
Given:
- Stable branches are moving slowly
- The release preparation MR workflow of removing the "Draft" status after the latest pipeline started (e.g. gitlab-org/gitlab!83013 (comment 877276434))
- Merged results pipeline currently don't run on "Draft" MRs
We're disabling the RemindMergedMrDeviatingFromGuideline
processor for MRs that target stable branches.
The ideal solution would be that Draft MRs run Merged Results pipelines, as explained in gitlab-org/gitlab#247067 (comment 878703843).
For reference, this builds upon:
Expected impact & dry-runs
Release preparation MRs won't be bothered by the RemindMergedMrDeviatingFromGuideline
processor anymore.
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 => -
Engineering week-in-review
-
Edited by Rémy Coutable