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
It would be super helpful to have a team base permission. We generally have 3 "teams": readers (non-engineering collaborators), engineers (maintainer) and a couple of "owner level" users. It would be super helpful to be able to give teams, or people, a base permission across the organization's repositories. For example, all engineers get the maintainer permission, all non-engineers get the reader permission, etc.
Right now the only way I found is to set the base permission to read, then add each individual repository to the engineering team and manually give them a maintainer permission per repository. Quite a manual process which is prone to be forgotten anytime someone creates a repo.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Select Topic Area
Product Feedback
Body
It would be super helpful to have a team base permission. We generally have 3 "teams": readers (non-engineering collaborators), engineers (maintainer) and a couple of "owner level" users. It would be super helpful to be able to give teams, or people, a base permission across the organization's repositories. For example, all engineers get the maintainer permission, all non-engineers get the reader permission, etc.
Right now the only way I found is to set the base permission to read, then add each individual repository to the engineering team and manually give them a maintainer permission per repository. Quite a manual process which is prone to be forgotten anytime someone creates a repo.
Beta Was this translation helpful? Give feedback.
All reactions