Google Git
Sign in
chromium / playground / gerrit-cq / normal / 0a6841cac151d54a097ca5b60961a58ca47009ee
commit0a6841cac151d54a097ca5b60961a58ca47009ee[log] [tgz]
authorAndrii Shyshkalov <tandrii@chromium.org>Mon Sep 18 18:11:02 2017
committerAndrii Shyshkalov <tandrii@chromium.org>Mon Sep 18 18:11:26 2017
treefa79f0549d7ccacd6300a4084f7bda42ee95f3e1
parent3cea100052cfb8c37915ecae27fbfb9452d9d060 [diff]
Test https://crbug.com/765742#c3

Change-Id: I5274136206259b0f8b728a99f1a3b966f9871146
Reviewed-on: https://chromium-review.googlesource.com/671498
Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
1 file changed
tree: fa79f0549d7ccacd6300a4084f7bda42ee95f3e1
  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.
git cl upload