Lines Matching +full:node +full:- +full:core +full:- +full:utils
9 confirm that they are using [two-factor authentication][]. It will not be
10 possible to add them to the organization if they are not using two-factor
15 * Suggest the new Collaborator install [`node-core-utils`][] and
23 [Who to CC in the issue tracker][who-to-cc].
28 * [local setup](#local-setup)
29 * [project goals & values](#project-goals--values)
30 * [managing the issue tracker](#managing-the-issue-tracker)
31 * [reviewing PRs](#reviewing-prs)
32 * [landing PRs](#landing-prs)
37 * Make sure you have whitespace=fix: `git config --global --add
40 * Branches in the `nodejs/node` repository are only for release lines
42 * `git remote add upstream git://github.com/nodejs/node.git`
45 * `git remote update -p` OR `git fetch --all`
46 * `git merge --ff-only upstream/master` (or `REMOTENAME/BRANCH`)
48 * Membership: Consider making your membership in the Node.js GitHub
59 The project has two venues for real-time discussion:
60 * [`#nodejs-dev`](https://openjs-foundation.slack.com/archives/C019Y2T6STH) on
61 the [OpenJS Foundation](https://slack-invite.openjsf.org/)
62 * `#node-dev` on [webchat.freenode.net](https://webchat.freenode.net/) is a
66 * Presence is not mandatory, but please drop a note there if force-pushing
74 * There are some higher-level goals and values
90 * [**See "Labels"**](./doc/guides/onboarding-extras.md#labels)
91 * There is [a bot](https://github.com/nodejs-github-bot/github-bot) that
96 * `semver-{minor,major}`:
98 `semver-major` label
99 * When adding a `semver-*` label, add a comment explaining why you're adding
101 * Please add the [`author-ready`][] label for PRs, if applicable.
103 * See [Who to CC in the issue tracker][who-to-cc].
114 organization (not just Collaborators on Node.js core) have access. Its
117 [here](https://github.com/nodejs/admin/blob/master/Moderation-Policy.md).
125 * It is tempting to micro-optimize. Don't succumb to that temptation. We
137 * There is a minimum waiting time which we try to respect for non-trivial
140 * For non-trivial changes, leave the pull request open for at least 48 hours.
158 * What belongs in Node.js:
160 * If Node.js itself needs it (due to historical reasons), then it belongs in
161 Node.js.
164 * Things that cannot be done outside of core, or only with significant pain
171 * You will be using `node-test-pull-request` most of the time. Go there now!
172 * Consider bookmarking it: <https://ci.nodejs.org/job/node-test-pull-request/>
184 the pull request is `https://github.com/nodejs/node/issues/7006`, then put
187 * If you need help with something CI-related:
188 * Use #node-dev (IRC) to talk to other Collaborators.
189 * Use #node-build (IRC) to talk to the Build WG members who maintain the CI
202 <!-- TODO(joyeechueng): provide examples about "one logical change" -->
207 <https://github.com/nodejs/node/commit/ce986de829457c39257cd205067602e765768fb0>
209 -1`
212 * Label your pull request with the `doc`, `notable-change`, and `fast-track`
214 * Run CI on the PR. Use the `node-test-pull-request` CI task.
216 for fast-tracking, land the PR.
217 * Leave a comment in the PR: `Please �� this comment to approve fast-tracking`.
220 * Be sure to add the `PR-URL: <full-pr-url>` and appropriate `Reviewed-By:`
222 * [`node-core-utils`][] automates the generation of metadata and the landing
223 process. See the documentation of [`git-node`][].
224 * [`core-validate-commit`][] automates the validation of commit messages.
225 This will be run during `git node land --final` of the [`git-node`][]
238 * [https://github.com/nodejs/readable-stream](https://github.com/nodejs/readable-stream)
242 Node.js project, where we have face-to-face discussions about our work on the
248 [Landing Pull Requests]: doc/guides/collaborator-guide.md#landing-pull-requests
249 …zation membership]: https://help.github.com/articles/publicizing-or-hiding-organization-membership/
250 [`author-ready`]: doc/guides/collaborator-guide.md#author-ready-pull-requests
251 [`core-validate-commit`]: https://github.com/nodejs/core-validate-commit
252 [`git-node`]: https://github.com/nodejs/node-core-utils/blob/master/docs/git-node.md
253 [`node-core-utils`]: https://github.com/nodejs/node-core-utils
254 [set up the credentials]: https://github.com/nodejs/node-core-utils#setting-up-credentials
255 [two-factor authentication]: https://help.github.com/articles/securing-your-account-with-two-factor…
256 …ile app]: https://help.github.com/articles/configuring-two-factor-authentication-via-a-totp-mobile…
257 [who-to-cc]: doc/guides/collaborator-guide.md#who-to-cc-in-the-issue-tracker