commit | 69e169cf5b5c1b23413f2bb3a56c61f8c9dcfb9d | [log] [tgz] |
---|---|---|
author | Andrii Shyshkalov <tandrii@chromium.org> | Tue Feb 21 09:01:49 2017 |
committer | Andrii Shyshkalov <tandrii@chromium.org> | Tue Feb 21 09:05:02 2017 |
tree | caa2a5efe3c12f6297436f4edf114be89f422399 | |
parent | b40ea028dfc969172752bde77f3e3f253647c00b [diff] |
Change bucket. BUG= Change-Id: I473c13b35ee6fad0db5bcbdff2b1a7eee4b930e0 Reviewed-on: https://chromium-review.googlesource.com/445697 Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
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. git cl upload
Does it work with numbers?