Forking a repository on GitHub is a common way to contribute to open-source projects or create a new project based on an existing one. However, when it comes to forking your own repository, things get a bit tricky. Clicking the Fork button on your own repository does nothing! (…other than a page refresh). For some reason, GitHub does not support creating forks from your own repository. But don’t worry, there’s a workaround using upstream remotes in Git.
How to Fork Your Own Repository Using Upstream Remotes
To create a fork-like setup for your own repository, follow these steps:
Create a new repository for your fork on GitHub. This will be your forked repository.
Clone your new forked repository using git clone.
Add your original repository as an upstream remote in your forked repository. This will allow you to pull in changes from your original repository to your forked repository.
Update your fork with all the changes from your original repository using git pull.
Push your new fork back to GitHub using git push.
By following these steps, you can achieve a similar setup to forking your own repository, allowing you to work on a new project while keeping your original repository as the main source.
Limitations of Forking Your Own Repository
While this workaround allows you to create a fork-like setup, it’s important to note that it’s not a true fork. There are a few limitations to keep in mind:
You cannot create pull requests between your original repository and the forked repository.
Your forked repository will not be listed under your profile’s “Repositories” section.
The forked repository will not be automatically updated with changes from your original repository.
If you need a true fork of your repository, consider creating a new GitHub account or using an organization account to fork your repository.