1Commit Queue Keywords 2===================== 3 4COMMIT 5------ 6 7If you are working on experimental code and do not want to risk accidentally 8submitting the change via the CQ, then you can mark it with "COMMIT=false". 9The CQ will immediately abandon the change if it contains this option. 10To do a dry run through the CQ please use Gerrit's [CQ Dry Run](https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/G5-X0_tfmok) feature. 11 12 COMMIT=false 13 14The CQ will run through its list of verifiers (reviewer check, trybots, tree check, 15presubmit check), and will close the issue instead of committing it. 16 17No-Dependency-Checks 18-------------------- 19 20 No-Dependency-Checks: true 21 22The CQ rejects patchsets with open dependencies. An open dependency exists when a CL 23depends on another CL that is not yet closed. You can skip this check with this keyword. 24 25CQ_INCLUDE_TRYBOTS 26------------------ 27 28Allows you to add arbitrary trybots to the CQ's list of default trybots. 29The CQ will block till these tryjobs pass just like the default list of tryjobs. 30 31This is the format of the values of this keyword: 32 33 CQ_INCLUDE_TRYBOTS=bucket1:bot1,bot2;bucket2:bot3,bot4 34 35Here are some real world examples: 36 37 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_chromium_asan_rel_ng 38 39 CQ_INCLUDE_TRYBOTS=skia.primary:Test-Win10-Clang-ShuttleC-GPU-GTX960-x86_64-Debug-All-ANGLE 40 41 42No-Tree-Checks 43-------------- 44 45If you want to skip the tree status checks, to make the CQ commit a CL even if the tree is closed, 46you can add the following line to the CL description: 47 48 No-Tree-Checks: true 49 50This is discouraged, since the tree is closed for a reason. However, in rare cases this is acceptable, 51primarily to fix build breakages (i.e., your CL will help in reopening the tree). 52 53No-Presubmit 54------------ 55 56If you want to skip the presubmit checks, add the following line to the CL description: 57 58 No-Presubmit: true 59 60No-Try 61------ 62 63If you cannot wait for the try job results, you can add the following line to the CL description: 64 65 No-Try: true 66 67The CQ will then not run any try jobs for your change and will commit the CL as soon as the tree is open, assuming the presubmit check passes. 68 69NO_MERGE_BUILDS 70--------------- 71 72This keyword prevents the Skia build masters from building this commit with others. Use it when your 73commit may have effects that you don't want mis-attributed to other commits. Just include the keyword 74somewhere in the commit message: 75 76 NO_MERGE_BUILDS 77