Skip to content

Commit f127ae3

Browse files
juanarboltargos
juanarbol
authored and
targos
committed
doc: clarify when not to run CI on docs
Collaborators won't need to run CI on documentation-only changes. PR-URL: #33101 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Andrey Pechkurov <apechkurov@gmail.com>
1 parent 7c8b0d2 commit f127ae3

1 file changed

Lines changed: 4 additions & 2 deletions

File tree

‎doc/guides/collaborator-guide.md‎

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -177,8 +177,10 @@ All pull requests must pass continuous integration tests. Code changes must pass
177177
on [project CI server](https://ci.nodejs.org/). Pull requests that only change
178178
documentation and comments can use GitHub Actions results.
179179

180-
Do not land any pull requests without passing (green or yellow) CI runs. If
181-
there are CI failures unrelated to the change in the pull request, try "Resume
180+
Do not land any pull requests without a passing (green or yellow) CI run.
181+
For documentation-only changes, GitHub Actions CI is sufficient.
182+
For all other code changes, Jenkins CI must pass as well. If there are
183+
Jenkins CI failures unrelated to the change in the pull request, try "Resume
182184
Build". It is in the left navigation of the relevant `node-test-pull-request`
183185
job. It will preserve all the green results from the current job but re-run
184186
everything else. Start a fresh CI if more than seven days have elapsed since

0 commit comments

Comments
 (0)