0

docs: Remove all references to the 'Tbr:' git footer

The rollout of the "mandatory code review" policy has dropped support
for TBR'ing a change. So this removes all references to the tbr footer
since it should no longer work.

Bug: None
Change-Id: I71ad4ed39d90834b9084bb400fa52d3d049ed971
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4126477
Reviewed-by: Struan Shrimpton <sshrimp@google.com>
Reviewed-by: Gary Tong <gatong@chromium.org>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1087195}
This commit is contained in:
Ben Pastene
2022-12-27 22:17:48 +00:00
committed by Chromium LUCI CQ
parent 07adcece37
commit fe6effd1a9
2 changed files with 0 additions and 9 deletions

@ -462,9 +462,6 @@ formats.
`-r foo@example.com` when running `git cl upload`.
* A comma-separated list of reviewer email addresses (e.g.
foo@example.com, bar@example.com).
* **Tbr:** The same format as the `R` footer, but indicates to the
commit queue that it can skip checking that all files in the change
have been approved by their respective `OWNERS`.
* **Cq-Include-Trybots:**
* A comma-separated list of trybots which should be triggered and
checked by the CQ in addition to the normal set.

@ -77,12 +77,6 @@ The Chromium CQ supports a variety of options that can change what it checks.
This should only be used for reverts to green the tree, since it skips try
bots and might therefore break the tree. You shouldn't use this otherwise.
* `Tbr: <username>`
[See policy](https://chromium.googlesource.com/chromium/src/+/HEAD/docs/code_reviews.md#TBR-To-Be-Reviewed)
of when it's acceptable to use TBR ("To be reviewed"). If a change has a TBR
line with a valid reviewer, the CQ will skip checks for LGTMs.
## FAQ
### What exactly does the CQ run?