From d2417d5c08389fd69e2a7b4511e3b5fadf41309b Mon Sep 17 00:00:00 2001 From: Robert Findley Date: Mon, 20 Sep 2021 15:17:19 -0400 Subject: [PATCH] gopls/doc: add instructions for the new "kokoro rerun" feature Change-Id: Idb7ed8ab7f736cac10be1e9d5592e1ffb3f048eb Reviewed-on: https://go-review.googlesource.com/c/tools/+/351090 Trust: Robert Findley Run-TryBot: Robert Findley Reviewed-by: Hyang-Ah Hana Kim gopls-CI: kokoro --- gopls/doc/contributing.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/gopls/doc/contributing.md b/gopls/doc/contributing.md index 307b601576..99e4529229 100644 --- a/gopls/doc/contributing.md +++ b/gopls/doc/contributing.md @@ -102,10 +102,8 @@ best-effort, and test failures may be skipped rather than fixed. Kokoro runs are triggered by the `Run-TryBot=1` label, just like TryBots, but unlike TryBots they do not automatically re-run if the "gopls-CI" result is -removed in Gerrit. In order to force a new run, you must upload a new patch -set. (Technically, Googlers can force a new run on an existing patch-set via an -internal Kokoro dashboard, but unfortunately this ability can't be made more -generally available). +removed in Gerrit. To force a re-run of the Kokoro CI on a CL containing the +`Run-TryBot=1` label, you can reply in Gerrit with the comment "kokoro rerun". ## Debugging