1 2--- 3title: "Commit Queue Keywords" 4linkTitle: "Commit Queue Keywords" 5 6--- 7 8 9See [CQ 10documentation](https://chromium.googlesource.com/chromium/src/+/main/docs/infra/cq.md) 11for more information. 12 13Options in the form "Key: Value" must appear in the last paragraph of the 14commit message to be used. 15 16 17Commit 18------ 19 20If you are working on experimental code and do not want to risk accidentally 21submitting the change via the CQ, then you can mark it with "Commit: false". 22The CQ will immediately abandon the change if it contains this option. 23To do a dry run through the CQ please use Gerrit's [CQ Dry 24Run](https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/G5-X0_tfmok) 25feature. 26 27 Commit: false 28 29The CQ will run through its list of verifiers (reviewer check, trybots, tree check, 30presubmit check), and will close the issue instead of committing it. 31 32 33No-Dependency-Checks 34-------------------- 35 36 No-Dependency-Checks: true 37 38The CQ rejects patchsets with open dependencies. An open dependency exists when a CL 39depends on another CL that is not yet closed. You can skip this check with this keyword. 40 41 42Cq-Include-Trybots 43------------------ 44 45Allows you to add arbitrary trybots to the CQ's list of default trybots. 46The CQ will block till these tryjobs pass just like the default list of tryjobs. 47 48This is the format of the values of this keyword: 49 50 Cq-Include-Trybots: bucket1:bot1,bot2;bucket2:bot3,bot4 51 52Multiple lines are allowed: 53 54 Cq-Include-Trybots: bucket1:bot1 55 Cq-Include-Trybots: bucket1:bot2 56 Cq-Include-Trybots: bucket2:bot3 57 Cq-Include-Trybots: bucket2:bot4 58 59Here are some real world examples: 60 61 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_asan_rel_ng 62 Cq-Include-Trybots: skia.primary:Test-Win10-Clang-ShuttleC-GPU-GTX960-x86_64-Debug-All-ANGLE 63 Cq-Include-Trybots: luci.skia.skia.primary:Build-Debian9-Clang-x86-devrel-Android_SKQP 64 65 FIXME: what bucket are skia bots in now? 66 67 68No-Tree-Checks 69-------------- 70 71If you want to skip the tree status checks, to make the CQ commit a CL even if 72the tree is closed, you can add the following line to the CL description: 73 74 No-Tree-Checks: true 75 76This is discouraged, since the tree is closed for a reason. However, in rare 77cases this is acceptable, primarily to fix build breakages (i.e., your CL will 78help in reopening the tree). 79 80 81No-Presubmit 82------------ 83 84If you want to skip the presubmit checks, add the following line to the CL description: 85 86 No-Presubmit: true 87 88 89No-Try 90------ 91 92If you cannot wait for the try job results, you can add the following line to 93the CL description: 94 95 No-Try: true 96 97The CQ will then not run any try jobs for your change and will commit the CL as 98soon as the tree is open, assuming the presubmit check passes. 99 100