Help
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Copilot Lvl 2
Message 1 of 5

Private repositories option grayed out under Member privileges in my organization

Solved! Go to Solution.

Under Memeber Privileges for my organization, in the grouping Repository Creation, the option for Private repositories is grayed out.

 

Private grayed outPrivate 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.

4 Replies
Highlighted
Solution
Copilot Lvl 2
Message 2 of 5

Re: Private repositories option grayed out under Member privileges in my organization

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.

Highlighted
Copilot Lvl 2
Message 3 of 5

Re: Private repositories option grayed out under Member privileges in my organization

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.  

Highlighted
Ground Controller Lvl 1
Message 4 of 5

Re: Private repositories option grayed out under Member privileges in my organization

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.

Highlighted
Copilot Lvl 2
Message 5 of 5

Re: Private repositories option grayed out under Member privileges in my organization

Source for the policy:

 

To allow members to create private repositories only, your organization must use GitHub Enterprise Cloud. For more information, see "About repository visibility."

 

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?