wiki: mention Cq-Include-Trybots can appear anywhere in the github PR description
Change-Id: I37d3e1826413788bc6c0d6995616a4c6467e6f94
GitHub-Last-Rev: 569b054551a374619425a7be0fedbfcdba719933
GitHub-Pull-Request: golang/wiki#14
Reviewed-on: https://go-review.googlesource.com/c/wiki/+/573975
Commit-Queue: Ian Lance Taylor <iant@golang.org>
Auto-Submit: Ian Lance Taylor <iant@golang.org>
Commit-Queue: qiulaidongfeng <2645477756@qq.com>
Reviewed-by: Ian Lance Taylor <iant@golang.org>
diff --git a/SlowBots.md b/SlowBots.md
index 0717143..ed1366e 100644
--- a/SlowBots.md
+++ b/SlowBots.md
@@ -22,7 +22,7 @@
Once you select the builds you would like to run, there are two ways to trigger the test runs:
-* **Blocking**: This is the recommended approach. Add the `Cq-Include-Trybots` git footer displayed in the dialog to the last paragraph of the commit message. Once a patch set with the updated commit message is uploaded, vote `Commit-Queue+1` as usual. The additional builds are treated just like the default TryBots: failures will block submission and send email notifications, and the builds will automatically run on subsequent patch set (as long as the `Cq-Include-Trybots` line remains). Note that the `Cq-Include-Trybots` git footer will not be used if it's not in the last paragraph of the commit message. That is, it must be **right next to the `Change-Id` line without empty lines** (see screenshot below).
+* **Blocking**: This is the recommended approach. Add the `Cq-Include-Trybots` git footer displayed in the dialog to the last paragraph of the commit message. For CL sent via github, it is OK to appear anywhere in the description of github PR. Once a patch set with the updated commit message is uploaded, vote `Commit-Queue+1` as usual. The additional builds are treated just like the default TryBots: failures will block submission and send email notifications, and the builds will automatically run on subsequent patch set (as long as the `Cq-Include-Trybots` line remains). Note that the `Cq-Include-Trybots` git footer will not be used if it's not in the last paragraph of the commit message. That is, it must be **right next to the `Change-Id` line without empty lines** (see screenshot below).
* **Advisory only**: Clicking the "Add" button will immediately start running the tests (even without a `Commit-Queue+1` vote). These are completely one-off advisory builds only. Status and results will appear in the "Checks" section (seen screenshot below), but failing results will not block submission or send an email notification. These builds will not automatically run again when a new patch set is uploaded.
