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 1 commit
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
Prev Previous commit
Next Next commit
fixup
  • Loading branch information
@ronag
ronag committed Jan 28, 2020
commit 202a18339c2d624041e1ad876836d5baaaba7777
18 changes: 9 additions & 9 deletions COLLABORATOR_GUIDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -191,12 +191,6 @@ everything else. Start a fresh CI if more than seven days have elapsed since
the original failing CI as the compiled binaries for the Windows and ARM
platforms are only kept for seven days.

Some of the CI Jobs may require `GIT_REMOTE_REF` which is the remote portion
of Git refspec. To specify the branch this way `refs/heads/BRANCH` is used
(i.e for `master` -> `refs/heads/master`).
For pull requests it will look like `refs/pull/PR_NUMBER/head`
(i.e. for PR#42 -> `refs/pull/42/head`).

#### Useful CI Jobs

* [`node-test-pull-request`](https://ci.nodejs.org/job/node-test-pull-request/)
Expand All @@ -222,12 +216,18 @@ 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`).

#### Starting a CI Job

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:
You generally need to enter only one or both of the following options
in the form:

* `GIT_REMOTE_REF`: Change this to refs/pull/NNNNN/head where NNNNN is the pull
request ID.
* `GIT_REMOTE_REF`: Change to the remote portion of Git refspec.
Comment thread
ronag marked this conversation as resolved.
Outdated
To specify the branch this way `refs/heads/BRANCH` is used
Comment thread
ronag marked this conversation as resolved.
Outdated
(i.e for `master` -> `refs/heads/master`).
Comment thread
ronag marked this conversation as resolved.
Outdated
For pull requests it will look like `refs/pull/PR_NUMBER/head`
Comment thread
ronag marked this conversation as resolved.
Outdated
(i.e. for PR#42 -> `refs/pull/42/head`).
Comment thread
ronag 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.
Expand Down