Skip to content

docs: update collaborator guide with citgm instructions #31549

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ronag wants to merge 6 commits into from
Closed

docs: update collaborator guide with citgm instructions #31549

Changes from 2 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
300fe21
docs: update collaborator guide with citgm instructions
ronag Jan 28, 2020
45dd15f
fixup
ronag Jan 28, 2020
202a183
fixup
ronag Jan 28, 2020
519a4b2
fixup: TOC
ronag Jan 28, 2020
e044298
Update COLLABORATOR_GUIDE.md
ronag Jan 30, 2020
4c9502b
Apply suggestions from code review
ronag Jan 30, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions COLLABORATOR_GUIDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -222,6 +222,25 @@ not used in other CI test runs (such as tests in the `internet` or `pummel`
directories). It can also make sure tests pass when provided with a flag not
used in other CI test runs (such as `--worker`).

From the CI Job page, click "Build with Parameters" on the left side.

You generally need to enter only one or both of the following in the form:

* `GIT_REMOTE_REF`: Change this to refs/pull/NNNNN/head where NNNNN is the pull
request ID.
Comment thread
richardlau marked this conversation as resolved.
Outdated
* `REBASE_ONTO`: Change that to origin/master so the pull request gets rebased
Comment thread
ronag marked this conversation as resolved.
Outdated
onto master. This can especially be important for pull requests that have been
open a while.

Look at the list of jobs on the left hand side under "Build History" and copy
the link to the one you started (which will be the one on top, but click
through to make sure it says something like "Started 5 seconds ago"
(top right) and "Started by user ...".

Copy/paste the URL for the job into a comment in the pull request.
[`node-test-pull-request`](https://ci.nodejs.org/job/node-test-pull-request/)
is an exception where the GitHub bot will automatically post for you.

### Internal vs. Public API

All functionality in the official Node.js documentation is part of the public
Expand Down