About repository visibility changes
Organization owners can restrict the ability to change repository visibility to organization owners only. For more information, see "Restricting repository visibility changes in your organization."
We recommend reviewing the following caveats before you change the visibility of a repository.
Warning: Changes to the visibility of a large repository or repository network may affect data integrity. Visibility changes can also have unintended effects on forks. GitHub recommends the following before changing the visibility of a repository network.
-
Wait for a period of reduced activity on your GitHub Enterprise Server instance.
-
Contact your site administrator before proceeding. Your site administrator can contact GitHub Enterprise Support for further guidance.
Making a repository private
- GitHub Enterprise Server will detach public forks of the public repository and put them into a new network. Public forks are not made private.
- If you change a repository's visibility from internal to private, GitHub will remove forks that belong to any user without access to the newly private repository. The visibility of any forks will also change to private. For more information, see "What happens to forks when a repository is deleted or changes visibility?"
- Anonymous Git read access is no longer available. For more information, see "Enabling anonymous Git read access for a repository."
Making a repository internal
- Any forks of the repository will remain in the repository network, and GitHub Enterprise Server maintains the relationship between the root repository and the fork. For more information, see "What happens to forks when a repository is deleted or changes visibility?"
Making a repository public
- GitHub Enterprise Server will detach private forks and turn them into a standalone private repository. For more information, see "