How to Make a GitHub Repository Private?

GitHub repositories can store code and projects, and they are either public (visible to everyone) or private (restricted to you and invited collaborators). Making your repository private ensures that only authorized users have access to your code, protecting sensitive or proprietary information.

This blog explains how to make your GitHub repository private.

Why Make a Repository Private?

1. Confidentiality: Keep proprietary code and projects secure.
2. Collaboration Control: Limit access to specific team members or collaborators.
3. Testing and Experimentation: Develop new features or ideas without public scrutiny.

---

Prerequisites

1. GitHub Account: Ensure you have an account and are signed in.
2. Repository Ownership: You must own the repository or have administrative permissions.
3. GitHub Plan: Free accounts can create private repositories, but additional features may require a paid plan.

---

Step-by-Step Guide to Make a Repository Private

1. Log In to GitHub

• Visit GitHub and log in with your credentials.

---

2. Navigate to Your Repository

• Click on your profile picture in the top-right corner.
• Select Your Repositories from the dropdown.
• Choose the repository you want to make private.

---

3. Go to Repository Settings

• On the repository’s main page, click the Settings tab in the navigation bar.

---

4. Change Visibility

• Scroll down to the Danger Zone section.
• Locate the Change repository visibility option.
• Click the Change visibility button.

---

5. Confirm Your Action

• A prompt will appear asking for confirmation.
• Read the warning about potential impacts on forks (if any).
• Type the repository name to confirm.
• Click the I understand, change repository visibility button.

---

What Happens When You Make a Repository Private?

1. Public Access is Revoked: The repository will no longer be visible to users who are not collaborators.
2. Collaborators Retain Access: Existing collaborators still have access unless explicitly removed.
3. Forks Are Restricted: Public forks of the repository remain public, but new forks cannot be created unless the repository is made public again.

---

Best Practices

1. Review Collaborators: Before making a repository private, ensure the right collaborators are assigned roles.
2. Check Repository Settings: Adjust permissions to suit your project\u2019s needs after changing visibility.
3. Communicate with Your Team: Notify collaborators about the change to avoid confusion.

---

Common Issues and Solutions

1. No Option to Change Visibility

• Cause: You lack administrative privileges.
• Solution: Contact the repository owner or administrator.

2. Unable to Access Private Repositories

• Cause: You are not added as a collaborator.
• Solution: Request access from the repository owner.

---

Conclusion

Making a GitHub repository private is a straightforward process that enhances security and access control. Whether you’re safeguarding intellectual property or limiting access to an active project, private repositories are an excellent way to collaborate securely.

By following the steps above and implementing best practices, you can ensure your code stays protected and accessible only to the right people.