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}
The current merge process for Phase 3 (late beta/stable) doesn't cover
cases where it's unclear whether the severity of the issue meets the
requirements for merging. This CL adds a segment to tell the engineer to
consult the TPM/their manager.
Bug: 1015723
Change-Id: Ia8406f47be7e0ed6ce87b6f4b3bf4cc9ecca78ad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1868213
Reviewed-by: Josafat Garcia <josafat@chromium.org>
Commit-Queue: Alan Cutter <alancutter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707265}
This makes our merge guidelines more permissive for feature work
which is gated behind a flag.
Change-Id: I1b65711006cf04e754570d55c16a12b51ed782f5
Reviewed-on: https://chromium-review.googlesource.com/958035
Reviewed-by: Krishna Govind <govind@chromium.org>
Commit-Queue: Alex Mineer <amineer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543551}
We'll start to store process documentation in MD in the source tree.
Add a "process" folder to the docs/ directory, and add release
blocking guidelines as initial content.
R=dpranke
CC=abdulsyed,cmasso,kerz
Bug:
Change-Id: I3270b5a94da9eb6df79a27361d91d00458aa2a1b
Reviewed-on: https://chromium-review.googlesource.com/529884
Commit-Queue: Alex Mineer <amineer@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#479053}
