Timeline for How do I update or sync a forked repository on GitHub?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 28, 2020 at 22:41 | comment | added | AxeEffect | This is a perfect solution if you don't have to pull many times from the original repo, or the project forked is relatively simple. | |
| Apr 17, 2019 at 2:34 | comment | added | Marc.2377 |
@LightCC This is not different than pulling from a previously added remote at all, except for the fact that you haven't added a remote. So the disadvantage is that you'll have to enter the full repository URL everytime you want to pull.
|
|
| Sep 11, 2017 at 20:23 | comment | added | Rafael Z. B. Bravo | it does work like a normal pull from a remote branch. If you did X commits on your local repo and now you are Y commits behind the original repo, it will bring the Y commits to your local branch and, probably, get you some conflicts to resolve. | |
| Sep 11, 2017 at 7:30 | comment | added | LightCC | Are there limitations on this? i.e. does it apply only to cases where you have not added commits, merges, pull requests, or had pull requests merged into upstream since the last update? | |
| Sep 8, 2017 at 2:00 | history | answered | Rafael Z. B. Bravo | CC BY-SA 3.0 |