Clone this repo:
  1. 9a5e6ae Remove rietveld from CQ. by Andrii Shyshkalov · 10 days ago master
  2. 4394394 More playing with cq.cfg. by Andrii Shyshkalov · 5 weeks ago
  3. 3760c93 Bump luci-config. by Andrii Shyshkalov · 5 weeks ago
  4. 0040949 Bump. by Andrii Shyshkalov · 5 weeks ago
  5. 0a6841c Test https://crbug.com/765742#c3 by Andrii Shyshkalov · 5 weeks ago

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