4 ms·
Not through the GitHub interface, no. But you can copy all files in a repository and create a new repository. IIRC there's a way to retain the history via this
by Manuel_D 2y ago
Not through the GitHub interface, no. But you can copy all files in a repository and create a new repository. IIRC there's a way to retain the history via this process as well.
- make3 2y agoThat's not the GitHub concept / almost trademark of "fork" anymore though, which is what your parent was talking about
- a1o 2y agoI mean it's git, just git init, git remote add for origin and upstream, origin pointing to your private, git fetch upstream, git push to origin.
- mckn1ght 2y agoYou can create a private repository on GitHub, clone it locally, add the repo being "forked" from as a separate git remote (I usually call this one "upstream" and my "fork", well, "fork"), fetch and pull from upstream, then push to fork.
- shkkmo 2y agoAll you should have to do is just clone the repo locally and then create a blank GitHub repository, set it as the/a remote and push to it.
- JyB 2y agoThat’s beside the point. The article is specifically about « GitHub forks » and their shortcomings. It’s unrelated to pushing to distinct repositories not magically ´linked’ by the GH « fork feature ».