| commit | 4291398b3f44bce7f8c6cd699f25ec0c869c60f0 | [log] [tgz] |
|---|---|---|
| author | Andrii Shyshkalov <[email protected]> | Mon Jul 30 22:06:12 2018 |
| committer | Andrii Shyshkalov <[email protected]> | Fri Aug 03 16:16:37 2018 |
| tree | 2929550e17d6c3a47e8c30de7ed8169b348d2e32 | |
| parent | 0f0efa10e9042c6d3196902b8f63234ad3efcad0 [diff] |
cq.cfg: remove cq_name. TBR=mknyszek Bug: 866476 Change-Id: I2286ba38ba70de3a79fed31ef136009e4aa25cef Reviewed-on: https://chromium-review.googlesource.com/1155590 Reviewed-by: Andrii Shyshkalov <[email protected]> Commit-Queue: Andrii Shyshkalov <[email protected]>
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:
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