Menu
My organisation has a main repo called org/A.git. I forked it as me/A.git to Github first. My organisation admin made org/A.git private, which broke the fork. He then changed settings which would allow forking private repositories. me/A.git is still not a fork but a simple clone. How can I make me/A.git a fork again, without having to:
org/A.git again which would result in me/A-1.git.me/A.git.me/A-1.git to me/A.git.me/A.git.I want to avoid the above 4 steps because I have additional contributors as well as branches in the original me/A.git and taking care of all that is just cumbersome for something which seems to be so simple.
809
Any public Git repository can be forked or cloned. A fork creates a completely independent copy of Git repository. In contrast to a fork, a Git clone creates a linked copy that will continue to synchronize with the target repository.
In this model, you fork the project repository to your own account using the GitHub website. You can then clone the forked repository to your desktop as you would any other repo. Typically you would create a working branch on the local copy of the repo, edit the documents, then push the changes to GitHub.
This is very, very, very old... However, I recently faced a similar circumstance myself, and contacted GitHub Support. For me, it wasn't that it was a fork originally and then it was broken, but rather I created my own repo manually before understanding what a fork was (still new to Git). GitHub Support confirmed there was no way to do it, unfortunately.
The quote from them:
Thanks for reaching out! Sorry for the trouble, but it isn't possible to attach a repository as a fork of another in this kind of situation -- repositories can't move from one fork network to another, or to a network they were not originally created from.
53
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
