How to Change a Public Repository to Private on GitHub?

GitHub offers developers the flexibility to make their repositories either public or private. Public repositories are visible to anyone on the internet, while private repositories restrict access, allowing only designated users to view and contribute to the code. As your project evolves, you may decide to make a public repository private, especially if it contains sensitive information or is no longer meant to be shared openly.

In this blog, we’ll go over the steps for changing a public repository to private on GitHub, explaining how to ensure your project’s visibility and access settings meet your needs.

Why Make a GitHub Repository Private?

There are several reasons to consider making a public repository private:

• Security: Keeping code and sensitive information (like API keys or environment configurations) private reduces the risk of accidental exposure.
• Professionalism: Some codebases are better kept private until they are refined and ready for public release.
• Access Control: With a private repository, you have full control over who can access and collaborate on your project.

---

Prerequisites

1. GitHub Account: You must have a GitHub account to manage repositories. You can sign up for one at github.com if you don’t already have one.
2. Repository Ownership or Access: Only the repository owner or collaborators with the necessary permissions can change a repository’s visibility settings.

---

Step-by-Step Guide to Make a GitHub Repository Private

Follow these simple steps to change your public repository to private.

---

Step 1: Log In to GitHub

1. Open your preferred web browser and go to github.com.
2. Log in to your GitHub account using your username and password.

---

Step 2: Navigate to Your Repository

1. From your GitHub dashboard, click on Your repositories or navigate to the Repositories tab in your profile.
2. Find the public repository you want to make private and click on its name to open it.

---

Step 3: Access the Repository Settings

1. Once you’re in the repository, go to the Settings tab at the top of the repository page.
2. The settings menu is where you can modify various repository details, including visibility, access, and permissions.

---

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 Change repository visibility option.
3. Click the Change visibility button next to this option.

---

Step 5: Confirm the Visibility Change

1. A dialog box will appear, asking you to confirm the change from Public to Private.
2. Read the confirmation message carefully. Changing a repository from public to private will restrict access to only those you specifically invite.
3. Type the repository name in the text box provided to confirm the action (GitHub requires this as an extra measure to ensure you understand the change).
4. Click the I understand, change repository visibility button.

---

Step 6: Verify the Repository’s New Private Status

1. After confirming, GitHub will make your repository private.
2. You’ll notice a lock icon next to your repository name, indicating that it is now private.
3. Confirm the visibility change by refreshing the page or visiting the repository’s main page; the visibility should be updated to Private.

---

Additional Steps: Managing Collaborators and Permissions

Once your repository is private, only you and selected collaborators can access it. You may need to adjust permissions or invite specific users if you’re working in a team.

1. Go to the Collaborators and Teams Section:

• In the Settings menu, scroll up to the Collaborators and teams section.

1. Invite Collaborators:

• Click Add people and enter the GitHub usernames or emails of users you want to invite.
• Assign them a role (such as Read, Write, or Admin) based on the level of access they need.

1. Save Changes:

• Your selected collaborators will receive an invitation. Once they accept, they’ll be able to access the private repository according to the permissions you’ve set.

---

Important Considerations

Changing a public repository to private can have implications for users who previously had access to it. Here are some things to keep in mind:

• Cloned Repositories: Users who cloned your public repository before it became private can still access their local copy, but they won’t receive updates unless they are collaborators.
• Issues and Pull Requests: Any issues or pull requests made by users who are not collaborators will no longer be accessible to them.
• Action Logs: GitHub keeps a log of repository changes, including visibility changes, which can be reviewed in the Security & Analysis settings if needed.
• API and Webhook Integrations: If your repository is used by integrations, ensure that these are updated if needed to handle the change to private visibility.

---

Best Practices for Managing Private Repositories

1. Limit Access: Only invite collaborators who need direct access to the repository to reduce security risks.
2. Use Access Control: Set appropriate permission levels for each collaborator to maintain control over your codebase.
3. Regularly Review Access: Periodically review who has access to your repository, removing access for users who no longer need it.
4. Utilize GitHub Security Features: For additional security, GitHub offers features such as branch protection rules, secret scanning, and dependency alerts.

---

Conclusion

Changing a public repository to private on GitHub is straightforward and can enhance the security and control of your codebase. Whether for project confidentiality, access control, or collaboration purposes, understanding how to manage your repository’s visibility ensures that your code remains accessible only to those you trust.

With this guide, you can confidently make any repository private and manage access effectively on GitHub.