Google GitGoogle Git
Sign in
chromium/playground/gerrit-cq/normal/d70e08cc4f5a6132c8157022499151643b72bf1e
commit
d70e08cc4f5a6132c8157022499151643b72bf1e
[log]
author
Andrii Shyshkalov <tandrii@chromium.org>
Mon Feb 06 16:43:48 2017
committer
Commit Bot <commit-bot@chromium.org>
Mon Feb 06 16:44:46 2017
tree
7d02bbdcec901ca8c006e58401a6e6d1515156fa
parent
cee6b75bfeef6ae292d51cc87695fcf02ff1116c [diff]
Add gerrit_cq_ability to test CQ project.

And test CQ config verifier just deployed of version ecbbe0.

TBR=sergiyb@google.com
NOTRY=true
BUG=641422

Change-Id: Idda0352d257b7d0ecaf1556e4a02f578fa343683
Reviewed-on: https://chromium-review.googlesource.com/438186
Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>
Commit-Queue-Verified: Commit Bot <commit-bot@chromium.org>
Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
1 file changed
tree: 7d02bbdcec901ca8c006e58401a6e6d1515156fa
  1. infra/
  2. codereview.settings
  3. README.md
  4. test1.py
  5. test2.py
  6. 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.
git cl upload

Does it work with numbers?