-
-
Save gschivley/ca44422f0cf5de26cc1d9ea16a95fde3 to your computer and use it in GitHub Desktop.
How to move to a fork after cloning
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
So you've cloned somebody's repo from github, but now you want to fork it and contribute back. Never fear! | |
Technically, when you fork "origin" should be your fork and "upstream" should be the project you forked; however, if you're willing to break this convention then it's easy. | |
* Off the top of my head * | |
1. Fork their repo on Github | |
2. In your local, add a new remote to your fork; then fetch it, and push your changes up to it | |
git remote add my-fork [email protected] | |
git fetch my-fork | |
git push my-fork | |
Otherwise, if you want to follow convention: | |
1. Fork their repo on Github | |
2. In your local, rename your origin remote to upstream | |
git remote rename origin upstream | |
3. Add a new origin | |
git remote add origin [email protected] | |
4. Fetch & push | |
git fetch origin | |
git push origin |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment