diff options
| author |  rmistry <rmistry@google.com> | 2015-04-28 10:28:13 -0700 |
|---|---|---|
| committer |  Commit bot <commit-bot@chromium.org> | 2015-04-28 10:28:13 -0700 |
| commit | 38620209ca67535686c6b62a2185254ef119196a (patch) | |
| tree | 1e6f88c091ae36f32957a155cb71dbb0ac686448 /site/dev/contrib | |
| parent | 97025e34d3e5916ec5ae5363a9ac44b776d2c1dd (diff) | |
Update documentation for "COMMIT=false".
The meaning of "COMMIT=false" was changed in https://code.google.com/p/chromium/issues/detail?id=470609.
I have also updated the corresponding Chromium documentation in https://sites.google.com/a/chromium.org/dev/developers/testing/commit-queue
BUG=skia:
NOTRY=true
DOCS_PREVIEW= https://skia.org/?cl=1107343004
Review URL: https://codereview.chromium.org/1107343004
Diffstat (limited to 'site/dev/contrib')
| -rw-r--r-- | site/dev/contrib/cqkeywords.md | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/site/dev/contrib/cqkeywords.md b/site/dev/contrib/cqkeywords.md index a8b7ad453d..352cdf62ff 100644 --- a/site/dev/contrib/cqkeywords.md +++ b/site/dev/contrib/cqkeywords.md @@ -4,8 +4,10 @@ Commit Queue Keywords COMMIT ------ -If you want to test your CL through the commit queue but are not ready to commit -the changes yet, you can add the following line to the CL description: +If you are working on experimental code and do not want to risk accidentally +submitting the change via the CQ, then you can mark it with "COMMIT=false". +The CQ will immediately abandon the change if it contains this option. +To do a dry run through the CQ please use Rietveld's [dry run](https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/G5-X0_tfmok) feature. COMMIT=false |