chromium/src
0
Fork 0
Code Activity

[docs] Update Merge docs

Browse Source 
Adding instructions about associating
a CL to a merge request bug.

Change-Id: I2e1fffa6f8ae414e89b704f302891bfedf5d2f12
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6069091
Commit-Queue: Ben Mason <benmason@chromium.org>
Reviewed-by: Erhu Akpobaro <eakpobaro@google.com>
Cr-Commit-Position: refs/heads/main@{#1391588}
This commit is contained in:
Ben Mason
2024-12-04 11:23:43 +00:00
committed by Chromium LUCI CQ
parent e911da0bde
commit e8424ee216
1 changed files with 4 additions and 0 deletions

4
docs/process/merge_request.md

@ -163,6 +163,10 @@ ASAP so that it can be included in the next release built from the branch; if
you don't merge your cherry-pick soon after approval, it will eventually be
rejected for merge.
**NOTE:** Ensure you link to the bug that has merge approval for the relevant
milestone (Using `Bug=<bug id>` in your commit description). Not linking to a
bug that has approval can cause delay to your CL landing.
Once the cherry-pick has landed, a bot will update the *Merge* field with
*Merged-###* label and remove *Approved-###* if the commit references the issue.
If for some reason the commit did not reference the issue, manually update the