Skip to content

Commit

Permalink
Clarify maintainer role in github teams (#2196)
Browse files Browse the repository at this point in the history
Co-authored-by: Armin Ruech <7052238+arminru@users.noreply.github.com>
Co-authored-by: Daniel Gomez Blanco <mail@dangb.me>
  • Loading branch information
3 people committed Jul 11, 2024
1 parent 8e75d06 commit 08365e3
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion docs/how-to-configure-new-repository.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,8 +37,10 @@ by removing categories which overlap with issues.
* The `foo-maintainers` team should be a member of the `foo-approvers` team,
and the `foo-approvers` team should be a member of the `foo-triagers` team.
* Every member of `foo-maintainers` should be included explicitly in `foo-approvers`
and `foo-triagers` with the "Maintainer" GitHub privileges. This allows
and `foo-triagers` with the "Maintainer" role. This allows
repository maintainers to invite new approvers and triagers to the team.
* Every member of `foo-maintainers` should have the "Maintainer" role on the `foo-maintainers` team.
This allows repository maintainers to invite new maintainers to the team.
* The team `foo-triagers` has `Triage` permissions for the repository. If repository
is using the Project Boards, `foo-triagers` should have `Write` permissions to
have access to the Project Boards. Do not add members of `foo-triagers` to
Expand Down

0 comments on commit 08365e3

Please sign in to comment.