Don't nudge on merged or closed merge requests
What does this MR do and why?
Don't nudge on merged or closed merge requests
Here's an example nudge that we don't want on a merged merge request long ago: gitlab-org/gitlab!31654 (comment 966220822)
Expected impact & dry-runs
These are strongly recommended to assist reviewers and reduce the time to merge your change.
See https://gitlab.com/gitlab-org/quality/triage-ops/-/tree/master/doc/scheduled#testing-with-a-dry-run on how to perform dry-runs.
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
-