GerritAccess, LUCI: update vote names
LUCI trybots have become the default by now.
See https://groups.google.com/g/golang-dev/c/Oq1LDUmIyLg/m/QV9wEb75AAAJ.
Change-Id: Ib697a6509bcbbac7a893dd4fd4d9e19fe56d22a8
Reviewed-on: https://go-review.googlesource.com/c/wiki/+/566276
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
diff --git a/GerritAccess.md b/GerritAccess.md
index 13a4cd8..b3a1254 100644
--- a/GerritAccess.md
+++ b/GerritAccess.md
@@ -27,7 +27,7 @@
A Code-Review+2 vote means that you have read the change and are confident that it is correct and appropriate to submit. Typically, you should only Code-Review+2 code in directories or packages that you "own"; the exception is trivial and obviously correct changes. Note that all user-visible new features or changes—new API, new command-line flags, and so on—need to go through the [proposal process](https://go.dev/s/proposal-process). The CLs should reference the specific accepted proposal [in the commit message](/wiki/CommitMessage) (“For #NNN.”).
-When adding a Code-Review+2 vote, it is encouraged to also add Run-TryBots+1 and Auto-Submit+1: see the [auto-submit](#auto-submit) section below for details.
+When adding a Code-Review+2 vote, it is encouraged to also add Commit-Queue+1 and Auto-Submit+1: see the [auto-submit](#auto-submit) section below for details.
A Code-Review+1 vote means that you have read the change and believe it seems reasonable but aren’t making the definitive judgement that Code-Review+2 indicates. It also means you are confident the change does not introduce any sort of security vulnerability or other clearly inappropriate code change.
@@ -42,11 +42,12 @@
If you are reviewing a CL and believe it can be approved and submitted as is,
with no further changes, you can use the auto-submit functionality
to run tests and submit the CL if the tests pass.
-To do this, vote Code-Review+2 as well as Auto-Submit+1 and Run-TryBot+1. When the tests pass, Gopherbot will submit it.
+To do this, vote Code-Review+2 as well as Auto-Submit+1 and Commit-Queue+1. When the tests pass, Gopherbot will submit it.
More precisely, Gopherbot watches for and automatically submits CLs that
- - have Auto-Submit+1 and TryBot-Result+1 votes,
+ - have an Auto-Submit+1 vote,
+ - have a satisfied TryBots-Pass submit requirement,
- have the necessary code reviews,
- have no unresolved comments,
- aren't marked #wait-release,
diff --git a/LUCI.md b/LUCI.md
index 6186b25..ad93122 100644
--- a/LUCI.md
+++ b/LUCI.md
@@ -9,7 +9,7 @@
Voting Commit-Queue+1 asks CQ to run the CL on the TryBots.
When the TryBots finish, CQ will reply with results, \
-voting either TryBot-Result+1 (pass) or TryBot-Result-1 (fail). \
+voting either LUCI-TryBot-Result+1 (pass) or LUCI-TryBot-Result-1 (fail). \
Important results (e.g. failures) will also appear as chips at the top \
of the Gerrit page for the CL, under the commit message.
