Commit 7b123ec
committed
doc: improve description of the triagers team
PR-URL: #39833
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>1 parent 34c0701 commit 7b123ec
1 file changed
Lines changed: 7 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -15,15 +15,16 @@ | |||
| 15 | 15 | ||
| 16 | 16 | ## Triagers | |
| 17 | 17 | ||
| 18 | - Triagers assess newly-opened issues in the nodejs/node and nodejs/help | ||
| 19 | - repositories. There is no GitHub team for triagers at the moment. | ||
| 18 | + Triagers assess newly-opened issues in the [nodejs/node][] and [nodejs/help][] | ||
| 19 | + repositories. The GitHub team for Node.js triagers is @nodejs/issue-triage. | ||
| 20 | + Triagers are given the "Triage" GitHub role and have: | ||
| 20 | 21 | ||
| 21 | - Triagers have: | ||
| 22 | - * ability to label issues | ||
| 23 | - * ability to comment, close, and reopen issues | ||
| 22 | + * Ability to label issues and pull requests | ||
| 23 | + * Ability to comment, close, and reopen issues and pull requests | ||
| 24 | 24 | ||
| 25 | 25 | See: | |
| 26 | 26 | ||
| 27 | + * [List of triagers](./README.md#triagers) | ||
| 27 | 28 | * [A guide for triagers](./doc/guides/contributing/issues.md#triaging-a-bug-report) | |
| 28 | 29 | ||
| 29 | 30 | ## Collaborators | |
@@ -174,4 +175,5 @@ The TSC follows a [Consensus Seeking][] decision-making model per the | |||
| 174 | 175 | [Consensus Seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making | |
| 175 | 176 | [TSC Charter]: https://github.com/nodejs/TSC/blob/HEAD/TSC-Charter.md | |
| 176 | 177 | [collaborators discussion page]: https://github.com/orgs/nodejs/teams/collaborators/discussions | |
| 178 | + [nodejs/help]: https://github.com/nodejs/help | ||
| 177 | 179 | [nodejs/node]: https://github.com/nodejs/node | |
0 commit comments