chromium/src
0
Fork 0
Code Activity

docs: Augment commit checklist with CLI commands

Browse Source 
Bug: None
Change-Id: Ia41927b4ac624bbb97b49a4eb797066848552d97
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3781023
Reviewed-by: Wolfgang Beyer <wolfi@chromium.org>
Commit-Queue: Wolfgang Beyer <wolfi@chromium.org>
Auto-Submit: Thiago Perrotta <tperrotta@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1027152}
This commit is contained in:
Thiago Perrotta
2022-07-22 07:58:46 +00:00
committed by Chromium LUCI CQ
parent cbd1897d51
commit 6e6630b743
1 changed files with 6 additions and 0 deletions

6
docs/commit_checklist.md

@ -138,6 +138,8 @@ continue until each commit is squashed into the first commit.
An alternative way to squash your commits into a single commit is to do `git
commit --amend` in the previous step.
Alternatively you can also run `git squash-branch`.
## 12. Rebase your local repository
Rebasing is a neat way to sync changes from the remote repository and resolve
@ -197,6 +199,8 @@ Click `CQ Dry Run`. Fix any errors because otherwise the CL won't pass the
commit queue (CQ) checks. Consider waiting for the CQ Dry Run to pass before
notifying your reviewers, in case the results require major changes in your CL.
Alternatively you can run `git cl try`.
## 16. Add reviewers to review your code
Click `Find Owners` or run `git cl owners` to find file owners to review your
@ -271,6 +275,8 @@ blanket stamp if your CL makes significant changes to subsystems. Click
`Submit to CQ` (Commit-Queue +2) to both try your change in the commit queue
(CQ) and automatically land it if successful.
Alternatively you can run `git cl set-commit`.
Just because your CL made it through the CQ doesn't mean you're in the clear
yet. There might be internal non-public try job failures, or bugs that went
unnoticed during the code review process. Consider monitoring the