Skip to content

Commit

Permalink
Allow maintainers admin permissions on a case-by-case basis (#983)
Browse files Browse the repository at this point in the history
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
  • Loading branch information
dyladan and arminru authored Feb 25, 2022
1 parent 4c8bf8c commit 0853c18
Showing 1 changed file with 2 additions and 3 deletions.
5 changes: 2 additions & 3 deletions docs/how-to-configure-new-repository.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,11 +32,10 @@ for the repository.
4. The team `foo-approvers` has `Write` permissions for the repository.
5. The team `foo-maintainers` has `Maintain` permissions for the
repository.
In individual cases, for example, if this is required to allow maintainers to publish releases independently,
the team `foo-maintainers` can be granted `Admin` permissions instead.
6. Root-level `CODEOWNERS` file on the repository should include superset of
people from both `foo-approvers` and `foo-maintainers`.
7. Some repositories may include more individuals with `Admin` permissions.
Typically to help set up repository, CI, web hooks or other administrative
work.

![image](https://user-images.githubusercontent.com/9950081/57563719-d7b6b300-7355-11e9-9ebb-3c4f549336bc.png)

Expand Down

0 comments on commit 0853c18

Please sign in to comment.