Commit f9a655b4 authored by Max Woolf's avatar Max Woolf

Clarify process for maintainers merging their own MRs

parent 192e2526
...@@ -403,6 +403,12 @@ your own suggestions to the merge request. Note that: ...@@ -403,6 +403,12 @@ your own suggestions to the merge request. Note that:
has more than one commit, then see the note below about rewriting has more than one commit, then see the note below about rewriting
commit history. commit history.
As a maintainer, if a merge request that you authored has received all required approvals, it is acceptable to show a [bias for action](https://about.gitlab.com/handbook/values/#bias-for-action) and merge your own MR, if:
- The last maintainer to review intended to start the merge and did not, OR
- The last maintainer to review started the merge, but some trivial chore caused the pipeline to break. For example, the MR might need a rebase first because of unrelated pipeline issues, or some files might need to be regenerated (like `gitlab.pot`).
- "Trivial" is a subjective measure but we expect project maintainers to exercise their judgement carefully and cautiously.
When ready to merge: When ready to merge:
WARNING: WARNING:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment