Google Git
Sign in
chromium / playground / gerrit-cq / normal / 9a5e6aef0a1c70b8b2d1ee342057e6285310a57b
commit9a5e6aef0a1c70b8b2d1ee342057e6285310a57b[log] [tgz]
authorAndrii Shyshkalov <tandrii@chromium.org>Thu Oct 12 00:05:08 2017
committerAndrii Shyshkalov <tandrii@chromium.org>Thu Oct 12 00:05:51 2017
tree25896a58bb33c67f3b459c6e582b22f78c6223e2
parent43943948434171c06e58a652f98573da2e81ea37 [diff]
Remove rietveld from CQ.

Change-Id: I9704d17f050b17d4d817b31a0ae61e62cb92bf6e
Reviewed-on: https://chromium-review.googlesource.com/714493
Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>
1 file changed
tree: 25896a58bb33c67f3b459c6e582b22f78c6223e2
  1. infra/
  2. codereview.settings
  3. README.md
  4. test.cpp
  5. test1.py
  6. test2.py
  7. whitespace.txt
README.md

Normal CQ workflow.

First make sure you have proper codereview.settings like the one in this repo.

Committers set the CQ label to either 1 (Dry run) or 2 (Ready for CQ) which will automatically submit change after all conditions are met:

  • CQ verifiers pass the change.
  • Gerrit allows to submit it.

Clone it this normal way:

git clone https://chromium.googlesource.com/playground/gerrit-cq/normal

Initialize your repository first:

git new-branch feature
# hack, hack, hack
git add changed.file
git commit
# You can hack more, and commit again,
# but they'll all be squashed by default in git cl upload step.

# OK, now ask others for review:
git cl upload

# Make changes locally per review.
git add changed.file
git commit

# Now upload new patchset and trigger CQ dry run.
git cl upload -d