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.
- GitHub 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. 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."
- GitHub will detach private forks and turn them into a standalone private repository. For more information, see "What happens to forks when a repository is deleted or changes visibility?"
- If you're converting your private repository to a public repository as part of a move toward creating an open source project, see the Open Source Guides for helpful tips and guidelines.
- On GitHub Enterprise, navigate to the main page of the repository.
- Under your repository name, click
- Under "Danger Zone", to the right of to "Change repository visibility", click Change visibility.
- Select a visibility.
- To verify that you're changing the correct repository's visibility, type the name of the repository you want to change the visibility of.
- Click I understand, change repository visibility.