Skip to content

Commit a4975ca

Browse files
vsemozhetbytjasnell
authored andcommitted
doc: detail CI sub-tasks rerunning
PR-URL: #20200 Fixes: #20192 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
1 parent 0799b60 commit a4975ca

File tree

1 file changed

+8
-5
lines changed

1 file changed

+8
-5
lines changed

COLLABORATOR_GUIDE.md

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -199,11 +199,14 @@ status indicator.
199199

200200
Do not land any Pull Requests without passing (green or yellow) CI runs. If you
201201
believe any failed (red or grey) CI sub-tasks are unrelated to the change in the
202-
Pull Request, you may re-run the sub-task to try to see if it passes. If re-runs
203-
of all failed sub-tasks pass, it is permissible to land the Pull Request but
204-
only if the initial failures are believed in good faith to be unrelated to the
205-
changes in the Pull Request. Otherwise, reasonable steps must be taken to
206-
confirm that the changes are not resulting in an unreliable test.
202+
Pull Request, you may re-run the sub-task to try to see if it passes (just open
203+
the failed sub-task page and press the "Rebuild" button; be sure you are still
204+
logged in for this action). If re-runs of all failed sub-tasks pass (do not
205+
forget to provide the links for successfully rerun sub-tasks), it is permissible
206+
to land the Pull Request but only if the initial failures are believed in good
207+
faith to be unrelated to the changes in the Pull Request. Otherwise, reasonable
208+
steps must be taken to confirm that the changes are not resulting in an
209+
unreliable test.
207210

208211
#### Useful CI Jobs
209212

0 commit comments

Comments
 (0)