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-Win-MSVC-ShuttleC-GPU-GTX960-x86_64-Debug-ANGLE
40
41TBR
42---
43
44If you are a Skia committer and cannot wait for a review,
45then you can include the TBR keyword in your CL's description.
46
47Example:
48
49    TBR=rmistry@google.com
50
51NOTREECHECKS
52------------
53
54If you want to skip the tree status checks, to make the CQ commit a CL even if the tree is closed,
55you can add the following line to the CL description:
56
57    NOTREECHECKS=true
58
59This is discouraged, since the tree is closed for a reason. However, in rare cases this is acceptable,
60primarily to fix build breakages (i.e., your CL will help in reopening the tree).
61
62NOPRESUBMIT
63-----------
64
65If you want to skip the presubmit checks, add the following line to the CL description:
66
67    NOPRESUBMIT=true
68
69NOTRY
70-----
71
72If you cannot wait for the try job results, you can add the following line to the CL description:
73
74    NOTRY=true
75
76The 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.
77
78NO_MERGE_BUILDS
79---------------
80
81This keyword prevents the Skia build masters from building this commit with others. Use it when your
82commit may have effects that you don't want mis-attributed to other commits. Just include the keyword
83somewhere in the commit message:
84
85    NO_MERGE_BUILDS
86