chromium/src
0
Fork 0
Code Activity

[Docs] Update CQ doc to include 3 ways to stop the CQ

Browse Source 
1. Change the Commit-Queue value from +1 to 0 in Gerrit UI.
2. Upload a new patchset which triggers a new dry run.
3. Code-Review -1. This prevents a CL from landing.

Change-Id: I8cd0659a83deb469631f180e8a1192ba87fe8f94
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6254918
Reviewed-by: Ben Pastene <bpastene@chromium.org>
Commit-Queue: Darryl James <dljames@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1419021}
This commit is contained in:
dljames
2025-02-11 17:23:27 -08:00
committed by Chromium LUCI CQ
parent 24b81fe8a1
commit 45561553bc
1 changed files with 8 additions and 0 deletions

8
docs/infra/cq.md

@ -200,6 +200,14 @@ Please follow these general guidelines:
In both cases, when filing bugs, please include links to the build and/or CL
(including relevant patchset information) in question.
### How do I stop the CQ?
There are a few ways to do this. Here are 3:
1. Change the Commit-Queue value from +1 to 0 in Gerrit UI.
2. Upload a new patchset which triggers a new dry run (Ex: git cl upload -d).
3. Code-Review -1. This prevents a CL from landing.
### How do I add a new builder to the CQ?
There are several requirements for a builder to be added to the Commit Queue.