You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Permissions are very flexible in GitHub, and people can have access to a repository by being an organization member, collaborator, or specifically invited and empowered on the repository itself. To simplify matters, I created a nipreps/eddymotion team for "maintainers". By adding someone to this team, they get maintainer-level permissions on the repository and this team is also authorized to sign off on releases in the newly created Release environment (you will probably need admin to follow that link).
Org admins should feel free to add themselves or anybody else that should be a part of this team.
We can also be more explicit and rename to eddymotion-maint or similar, if you want to have a broader eddymotion team for less privileged contributors.
The text was updated successfully, but these errors were encountered:
Permissions are very flexible in GitHub, and people can have access to a repository by being an organization member, collaborator, or specifically invited and empowered on the repository itself. To simplify matters, I created a
nipreps/eddymotion
team for "maintainers". By adding someone to this team, they get maintainer-level permissions on the repository and this team is also authorized to sign off on releases in the newly created Release environment (you will probably need admin to follow that link).I have populated the team with a first pass group of people: https://github.com/orgs/nipreps/teams/eddymotion/members
Org admins should feel free to add themselves or anybody else that should be a part of this team.
We can also be more explicit and rename to
eddymotion-maint
or similar, if you want to have a broadereddymotion
team for less privileged contributors.The text was updated successfully, but these errors were encountered: