@@ -216,16 +216,14 @@ needs to be pointed out separately during the onboarding.
216
216
` git show --format=%B 6669b3857f0f43ee0296eb7ac45086cd907b9e94 `
217
217
* Collaborators are in alphabetical order by GitHub username.
218
218
* Optionally, include your personal pronouns.
219
- * The PR should include an addition to the
220
- [ mailmap] ( .mailmap ) file if the email
221
- being added to the collaborator list does not match the email used for
222
- commits. Otherwise tooling will not see the collaborator as being active and
223
- may suggest removing them. See
224
- [ gitmailmap] ( https://git-scm.com/docs/gitmailmap ) for information on the
225
- format of the mailmap file.
226
- * Add the ` Fixes: <collaborator-nomination-issue-url> ` to the commit message
219
+ * Commit, including a ` Fixes: <collaborator-nomination-issue-url> ` trailer
227
220
so that when the commit lands, the nomination issue url will be
228
221
automatically closed.
222
+ * Run ` tools/find-inactive-collaborators.mjs ` . If that command outputs your name,
223
+ amend the commit to include an addition to the [ mailmap] ( .mailmap ) file. See
224
+ [ gitmailmap] ( https://git-scm.com/docs/gitmailmap ) for information on the
225
+ format of the mailmap file.
226
+ * Push the commit to your own fork.
229
227
* Label your pull request with the ` doc ` , ` notable-change ` , and ` fast-track `
230
228
labels. The ` fast-track ` label should cause the Node.js GitHub bot to post a
231
229
comment in the pull request asking collaborators to approve the pull request
0 commit comments