How to Delete a Forked Repository in GitHub?

Forking a repository on GitHub is a powerful way to experiment with open-source projects, contribute to others’ code, and create a copy of any public repository in your own GitHub account. However, there may come a time when you no longer need the forked repository and want to delete it. Removing unnecessary forks keeps your GitHub profile clean and organized, making it easier to manage active projects. In this guide, we’ll walk you through the steps to safely delete a forked repository on GitHub.

What is a Forked Repository?

When you fork a repository on GitHub, you create a copy of someone else’s repository in your own GitHub account. This forked version is separate from the original, allowing you to make changes, test code, and even contribute to the original project without affecting the source repository. Forking is often used for:

• Experimenting with Code: Making changes in your own version without affecting the main project.
• Contributing to Open-Source Projects: Adding features or fixing bugs that can later be merged into the original repository.
• Personal Modifications: Customizing open-source projects for personal or team use.

Why Delete a Forked Repository?

Forked repositories can accumulate quickly on GitHub. If a fork is no longer relevant, removing it from your profile can help:

• Reduce Clutter: Fewer inactive repositories make it easier to manage active projects.
• Improve Profile Presentation: Keeping only important projects on your GitHub profile shows potential employers or collaborators a more polished profile.
• Free Up GitHub Resources: Deleting unused forks can prevent your GitHub from becoming overloaded with inactive projects.

Steps to Delete a Forked Repository

Deleting a repository is straightforward, but it’s an irreversible action. Here’s how to delete a forked repository on GitHub.

Step 1: Log In to Your GitHub Account

1. Open GitHub and log in to your account.
2. Once logged in, click on your profile icon in the top-right corner and select Your repositories from the dropdown menu to view your repositories.

Step 2: Locate the Forked Repository

1. In the Your repositories section, find the forked repository you want to delete.
2. Click on the repository name to open it. You’ll be taken to the main page of the forked repository.

Step 3: Go to Repository Settings

1. In the forked repository’s main page, navigate to the Settings tab. The Settings tab is located at the top of the page, to the right of the Insights and Security tabs.
2. Click on Settings to access the repository configuration options.

Step 4: Scroll Down to the Danger Zone

At the bottom of the Settings page, you’ll find a section labeled Danger Zone. This area includes options for actions that are irreversible, including deleting the repository.

Step 5: Delete the Repository

1. In the Danger Zone, locate the Delete this repository option.
2. Click on Delete this repository. A dialog box will appear, asking you to confirm the deletion.

Step 6: Confirm the Deletion

1. To confirm, you’ll need to type the name of the repository exactly as it appears (e.g., username/repository-name). This step helps ensure that you don’t accidentally delete the wrong repository.
2. After typing the repository name, click the I understand the consequences, delete this repository button.

GitHub will permanently delete the repository, removing all associated code, issues, pull requests, and other data. You will no longer see this repository in your GitHub account.

---

Things to Consider Before Deleting a Forked Repository

Deleting a repository is permanent, so consider the following before proceeding:

1. Back Up Any Changes You Want to Keep: If you’ve made changes to the forked repository that you might need in the future, consider creating a backup. You can either download the repository as a ZIP file or clone it to your local machine with:

   git clone https://github.com/username/repository-name.git

2. Unmerged Contributions: If you’ve submitted a pull request from your fork to the original repository, ensure that it has been reviewed or merged. Deleting your forked repository will close any active pull requests from that repository.
3. Check for Dependencies: If any of your other projects rely on code from this forked repository, ensure you no longer need the fork. Deleting it will break any links to the repository from other projects.

---

Alternative to Deleting a Fork: Archiving the Repository

If you aren’t ready to permanently delete the forked repository but want to minimize its visibility, consider archiving it. Archiving a repository makes it read-only, preventing new issues, pull requests, and commits while keeping the repository accessible.

Steps to Archive a Repository

1. Go to the repository’s Settings page.
2. In the Danger Zone, select Archive this repository.
3. Confirm by clicking I understand the consequences, archive this repository.

Summary

Deleting a forked repository on GitHub is an easy way to manage your profile and keep it organized. Here’s a quick recap of the process:

1. Log in to GitHub and navigate to your repositories.
2. Open the forked repository and go to the Settings tab.
3. Scroll to the Danger Zone and select Delete this repository.
4. Type the repository name to confirm deletion and click Delete.

By following these steps, you can confidently delete any forked repositories you no longer need. Keeping your GitHub profile up-to-date and clutter-free helps present a polished image to collaborators, employers, and others in the GitHub community.