Google Git
Sign in
chromium / playground / gerrit-cq / normal / 0040949bf6cf7a8cb376879ac883b845a6ce37ff
commit0040949bf6cf7a8cb376879ac883b845a6ce37ff[log] [tgz]
authorAndrii Shyshkalov <tandrii@chromium.org>Mon Sep 18 18:23:48 2017
committerAndrii Shyshkalov <tandrii@chromium.org>Mon Sep 18 18:24:08 2017
tree8d57a4d4c925c7d4ac3c1e30ada102c44820e533
parent0a6841cac151d54a097ca5b60961a58ca47009ee [diff]
Bump.

TBR=tandrii@chromium.org

Change-Id: I4e480ce3fbe6d94cbeb057b0ace30040207f02a6
Reviewed-on: https://chromium-review.googlesource.com/671623
Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
1 file changed
tree: 8d57a4d4c925c7d4ac3c1e30ada102c44820e533
  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