Managing permissions, membership, policy and teams #106329
Unanswered
jessehouwing
asked this question in
Enterprise
Replies: 1 comment 2 replies
-
I wholeheartedly agree. The current permissions system seems almost precision engineered to make managing who has access to what as inconvenient as possible, to the eventual end of having you give up and just set the "base permissions" as high as you can stomach, just so you don't have to constantly manually edit everything. The simple fact that you can't create a Team and configure it such that "this team has read access to every repository in the organization", "this team has write access to every repository in the organization", etc... it's maddening. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've been managing our gitHub enterprise for a few weeks now and I'm missing a lot of features in this area:
owner/name
for the repositories without allowing me to link, remove the user, or manage in any way.gh api
, but it usesbash
multi-line escapes (\
), this doesn't work inpwsh
andcmd
on windows, making it a real nuisance to edit the statement every time I copy/paste something from the docs. It would make sense not to include the multi-line separator at all when copying the contents using the 📋 button.Beta Was this translation helpful? Give feedback.
All reactions