4 ms·
git clone git@github.com:original/repo.git # make some commits git remote rename origin upstream # fork the repo on github git remote add origin
by kpcyrd 11y ago
git clone git@github.com:original/repo.git
# make some commits
git remote rename origin upstream
# fork the repo on github
git remote add origin git@github.com:your/repo.git
git fetch origin
git push -u origin master
- tenfingers 11y agoSure it's possible, however the only way to do it afterwards is to delete the repository and fork it manually again. Deleting the repository is only fine if there are no issue/wiki/data associated with it. The main problem is not omitting the "fork the repo on github" part voluntarily. Sometimes you're just not aware that you're pushing a repository which already has some ancestor on github, while you originally cloned from the main author's website instead. This has happened to me countless times. The graph network is totally useless in these cases.
- zimbatm 11y agoThis would be perfectly fine if all the project data was stored into git. Unfortunately github issues, comments, project metadata, webhook setup, team membership, ... are not part of the repository.
- TazeTSchnitzel 11y agoNot to mention past and outstanding pull requests.