I am currently working on a project that is a spinoff (fork) from a framework I have been working on.
This project is intended to be pretty generic, but now I need to fork the codebase again for a client of mine.
At this moment, I have created a custom branch for my client, but I'd rather have a standalone repository for this.
- Is is possible to 'fork a fork'?
- If not, what alternatives do I have?
Outline of the situation:
- Framework repository (original)
- Generic application repository (fork)
- (not yet) Client repository (fork of application)
- Generic application repository (fork)
Note: when trying to 'fork a fork' in Github, you will receive a notification that you have already forked the project:
I contacted GitHub support about this 'issue' and they confirmed this is not possible. Also, it is very unlikely that such a feature will be implemented in the future.
Of course it is possible. Unfortunately it must be done on the cmd line. After you create the base fork, create another new repo. Check out the base fork locally, add a remote to the new repo, and push to the new repo.
Answered in a comment by iFreilicht
Since this is the correct answer now, it is better to highlight it.
Simple answer: Yes and no.
No, for a single account as you are unable to create two repositories with the same name (and forks always have the same name).
Yes, for multiple accounts. So you could setup an organization for your second fork.