chromium/src
0
Fork 0
Code Activity

Update merge request docs to mention multiple changes

Browse Source 
Bug: 396131425
Change-Id: Iea66141d79b7f3ced1f94079506c8dd5c6aa9609
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6264023
Reviewed-by: Daniel Yip <danielyip@google.com>
Commit-Queue: Ben Mason <benmason@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1419911}
This commit is contained in:
Ben Mason
2025-02-13 08:06:47 -08:00
committed by Chromium LUCI CQ
parent 5ac5e81137
commit a48d7965cd
1 changed files with 5 additions and 2 deletions

7
docs/process/merge_request.md

@ -181,8 +181,11 @@ 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.
milestone. Not linking to a bug that has approval can cause delay to your CL
landing. If the merge request is for a single change, add `Fixed: <bug number>`
to the change description. If the merge request is for multiple changes, add
`Fixed: <bug number>` to the final change description, `Bug: <bug number>`
to all other change descriptions.
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.