How to Change a Public Repository to Private on GitHub?

GitHub offers both public and private repositories to meet different project needs, and sometimes a project that started publicly might need to be switched to private. Converting a public repository to private helps control access, limits visibility, and protects sensitive information.

In this guide, you’ll learn how to make a public GitHub repository private, as well as best practices for managing your repository’s privacy.

Why Make a Repository Private?

1. Confidentiality: Protect sensitive code or intellectual property.
2. Access Control: Restrict access to authorized collaborators only.
3. Professionalism: Keep unfinished projects or drafts private until they’re ready for public release.

Prerequisites

1. GitHub Account: You need an account on GitHub.
2. Repository Ownership or Admin Access: Only repository owners or users with admin access can change visibility.

Important Notes on Changing Repository Visibility

• Public to Private: When you change a public repository to private, users who have forked your repository will retain their forks.
• Free Accounts: GitHub offers private repositories even for free accounts, though these may have limited features compared to paid plans.

Step-by-Step Guide to Changing a Public Repository to Private

Step 1: Log into Your GitHub Account

Go to GitHub and log in with your credentials.

Step 2: Navigate to the Repository

In your GitHub dashboard, locate the repository you want to make private. Click on the repository name to go to its main page.

Step 3: Go to Settings

1. On the repository’s main page, find the Settings tab at the top of the page.
2. Click on Settings to open the repository settings.

Step 4: Change the Repository Visibility

1. Scroll down to the Danger Zone section at the bottom of the settings page.
2. Look for the option labeled Change repository visibility and click on Change visibility.
3. GitHub will prompt you to confirm this action. Click Make private to confirm.

Step 5: Confirm Repository Change

GitHub may ask for an additional confirmation by typing in the repository name or your GitHub password. This step is to ensure you’re fully aware of the implications of making the repository private.

Once confirmed, the repository will immediately switch from public to private.

Verifying the Change

To confirm that the repository is now private, go back to the repository’s main page. Next to the repository name, you should see a Private label instead of Public.

Best Practices for Managing Private Repositories

1. Review Collaborators: Now that the repository is private, review who has access and remove any unnecessary collaborators to maintain security.
2. Manage Access Control: For collaborative projects, use GitHub’s access control options to set permissions (e.g., Read, Write, Admin) for each collaborator.
3. Enable Security Features: Private repositories allow you to enable security features like vulnerability alerts, which help identify potential risks in your dependencies.
4. Regularly Update Repository Settings: Periodically review your repository settings to ensure they align with the project’s privacy and collaboration needs.

Common Issues and Troubleshooting

1. Visibility Option Not Available: If you don’t see the option to change visibility, make sure you have the necessary permissions (Owner/Admin).
2. Limited Access with Free Plan: Free GitHub accounts may have fewer options for private repositories. Consider upgrading if you need advanced features like multiple collaborators.
3. Forks Remain Public: Be aware that any public forks of your repository will remain public. You may need to coordinate with fork owners if you want them removed.

Conclusion

Switching a GitHub repository from public to private is a straightforward but crucial task for managing code privacy and access. By following these steps, you’ll have full control over who can access and contribute to your code, ensuring that your project remains secure and well-managed. Whether for confidential development or simply managing visibility, using private repositories effectively can enhance both your workflow and project integrity.