Private repositories option grayed out under Member privileges in my organization #23702
-
Under Memeber Privileges for my organization, in the grouping Repository Creation, the option for Private repositories is grayed out. I wish to enable this option so that only Private repos can be created. My organization is already marked private. We have a 5 seat paid account, which shows under billing that we can create unlimited private repositories. |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments
-
Okay, I have my answer. In case anyone else comes across this, it is an Enterprise Cloud feature, and all I have is Team access. |
Beta Was this translation helpful? Give feedback.
-
This is a ridiculous restriction. We are already paying for Private repos, and all I want to do is make sure one of my contractors doesn’t accidentally mark a repo as public. |
Beta Was this translation helpful? Give feedback.
-
I agree this is ridiculous. If you are paying for private repos, you should be able to ensure no one makes a mistake and changes a repo to be public! This is not an “enterprise” feature, it is a normal feature. |
Beta Was this translation helpful? Give feedback.
-
Source for the policy:
I agree this seems an excessive restriction, and common use case for non-enterprise users to not want to allow their employees/contractors to inadvertantly make a repo public and leak data/code. What is the best forum to respectfully request this feature be unlocked for GitHub Team customers? |
Beta Was this translation helpful? Give feedback.
-
It’s not Enterprise feature, you can change it in your Organization settings at /organizations/[ORG]/settings/member_privileges
|
Beta Was this translation helpful? Give feedback.
-
Maybe I am missing something. But what does forking have to do with new repository creation? |
Beta Was this translation helpful? Give feedback.
Okay, I have my answer. In case anyone else comes across this, it is an Enterprise Cloud feature, and all I have is Team access.