0

Link to doc about performing a merge

After getting merge approval, it can be hard to find details of how,
exactly, one merges a change into a branch. Since merge requests
automatically link to docs/process/merge_request.md, have a link from
there to the doc with the technical details.

Bug: None
Change-Id: I429064fa06c6b0562d15584c14c04a8347cbafff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2783154
Auto-Submit: Ian Barkley-Yeung <iby@chromium.org>
Reviewed-by: Alex Mineer <amineer@chromium.org>
Commit-Queue: Alex Mineer <amineer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#869642}
This commit is contained in:
Ian Barkley-Yeung
2021-04-06 19:00:35 +00:00
committed by Chromium LUCI CQ
parent ef8faa1309
commit 3af975e850

@ -154,3 +154,10 @@ automated process to take effect.
Manual merge reviews will be performed by release
owners and TPMs.
## Merge Process
Once the merge has been approved, please see
[How to merge a change to a release
branch](https://sites.google.com/a/chromium.org/dev/developers/how-tos/drover)
for technical details on performing the merge.