0

merge_request.md: Clarify how to find release branch on Chromium Dash

Bug: None
Change-Id: Ia5e57e9414e2160ed8c2e60564f63516620ef70e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3287144
Auto-Submit: Michael Cui <mlcui@google.com>
Reviewed-by: Alex Mineer <amineer@chromium.org>
Reviewed-by: Srinivas Sista <srinivassista@chromium.org>
Commit-Queue: Srinivas Sista <srinivassista@chromium.org>
Cr-Commit-Position: refs/heads/main@{#970881}
This commit is contained in:
mlcui
2022-02-14 22:52:06 +00:00
committed by Chromium LUCI CQ
parent e66bebaed7
commit eaa3e39577

@ -164,7 +164,8 @@ rejected for merge.
Select the "..." button in the Gerrit UI, then choose "Cherry Pick". When
prompted for a branch, enter *refs/branch-heads/####*, where #### corresponds
to the release branch you are merging to (available on
[Chromium Dash](https://chromiumdash.appspot.com/branches)).
[Chromium Dash](https://chromiumdash.appspot.com/branches) in the "Chromium"
column).
Once the cherry-pick CL is prepared, you can have it approved and landed by
adding Rubber Stamper (rubber-stamper@appspot.gserviceaccount.com) as a
@ -181,7 +182,8 @@ within 7 days of the original change; Googlers can learn more
The commands below should set up your environment to be able to successfully
upload a cherry-pick to a release branch, where *####* corresponds to the
release branch you are merging to (available on
[Chromium Dash](https://chromiumdash.appspot.com/branches)):
[Chromium Dash](https://chromiumdash.appspot.com/branches) in the "Chromium"
column):
```
$ gclient sync --with_branch_heads
@ -289,4 +291,4 @@ could have both *Merge-Approved-92* and *Merge-Rejected-91* at the same time).
| Merged | None | N/A; merge has already been landed, no further work required for given milestone |
| Rejected | Issue owner | Issue owner should re-add *Merge-Request-##* to escalate if they feel the merge was erroneously rejected and should be re-evaluated |
| TBD | Issue owner | Issue owner should evaluate if a merge is required, then remove *Merge-TBD-##* and replace it with *Merge-NA-##* (if no merge needed) or *Merge-Request-##* (if merge needed) |
| NA | None | N/A; merge is not required to the relevant milestone, no further work required for given milestone |
| NA | None | N/A; merge is not required to the relevant milestone, no further work required for given milestone |