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. 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?"
- If you're using GitHub Free for user accounts or organizations, some features won't be available in the repository after you change the visibility to private. For more information, see "GitHub's products."
- Any published GitHub Pages site will be automatically unpublished. If you added a custom domain to the GitHub Pages site, you should remove or update your DNS records before making the repository private, to avoid the risk of a domain takeover. For more information, see "Managing a custom domain for your GitHub Pages site."
- GitHub will no longer include the repository in the GitHub Archive Program. For more information, see "About archiving content and data on GitHub."
- GitHub Advanced Security features, such as code scanning, will stop working unless the repository is owned by an organization that has a license for Advanced Security. For more information, see "About GitHub Advanced Security."
Note: Internal repositories are available with GitHub Enterprise Cloud and GitHub Enterprise Server 2.20+. For more information, see "GitHub's products."
- Any forks of the repository will remain in the repository network, and GitHub 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?"
- 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. You can also take a free course on managing an open source project with GitHub Learning Lab. Once your repository is public, you can also view your repository's community profile to see whether your project meets best practices for supporting contributors. For more information, see "Viewing your community profile."
- The repository will automatically gain access to GitHub Advanced Security features.
For information about improving repository security, see "About securing your repository."
- On GitHub, 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.