Timeline for How do I update or sync a forked repository on GitHub?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 29, 2022 at 20:03 | history | edited | Innat | CC BY-SA 4.0 |
added 1 character in body
|
| Oct 19, 2021 at 18:34 | history | edited | Madhu Bhat | CC BY-SA 4.0 |
Added doc link
|
| May 8, 2021 at 0:31 | comment | added | li ki | For now, this function will first compare the branch name between the original and the forked repos. If the same name is found, the upstream of the branch in the fork is the branch with the same name in the original; if it is not found, the upstream will be the default branch (HEAD) of the original. This works fine in most cases, but if some branch modification has occurred in the original repo (e.g., adding or deleting a branch with the same name which already exists in the forked repo, or changing the default branch), the result of the sync may not match you expectations. | |
| May 7, 2021 at 23:44 | comment | added | li ki | I tried this and no PR was created, cool! And if your branch can be synced with a fast-forward merge, no divergence will occur. | |
| May 6, 2021 at 21:10 | history | answered | Madhu Bhat | CC BY-SA 4.0 |