Timeline for How do I update or sync a forked repository on GitHub?
Current License: CC BY-SA 3.0
29 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 9, 2021 at 15:26 | comment | added | Madhu Bhat | @Transformer your wish has been granted, albeit 4 years late ;) | |
| Feb 12, 2021 at 3:08 | comment | added | Time Killer | Why hasn't Github improved this stupid UI after so long? It requires at least 3 clicks to compare, and reload the page for a few seconds! waste time! | |
| Apr 9, 2020 at 12:09 | comment | added | Vladimir Djuricic | Best answer so far. It is interesting that I've intuitively moved to PR tab to do this, without too much thinking. However, I think it would be best to have REBASE FORK button next to (or instead) the FORK button. That was the first thing I've searched for - Rebase Fork button | |
| May 26, 2018 at 21:32 | comment | added | SwimBikeRun | What is the disadvantage of an ugly merge commit?? I don't get it. Just merge and you're done. Is there something I'm missing? | |
| Sep 26, 2017 at 20:41 | history | edited | MD XF | CC BY-SA 3.0 |
still works
|
| May 23, 2017 at 11:47 | history | edited | URL Rewriter Bot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Jan 24, 2017 at 3:32 | comment | added | Transformer | wouldnt it be better, with a simply update or sync button! | |
| Jan 12, 2017 at 17:16 | comment | added | Damian Yerrick | Say changes in my fork have primarily consisted of edits to documentation, which can be performed through web without cloning. Wouldn't performing "Stick to the command line instead - it's easy." require cloning the repository over my (possibly metered) Internet connection? | |
| Oct 28, 2016 at 20:44 | history | edited | Dan Dascalescu | CC BY-SA 3.0 |
added 584 characters in body
|
| Oct 28, 2016 at 20:40 | comment | added | Dan Dascalescu | The steps need an update; essentially, you need to compare your fork as a base, with the original as the head fork. However, the commit history won't be clean. You can either merge or squash+merge, which will leave you with a merge commit, or "Rebase and merge", which will give "This branch is X commits ahead, Y commits behind <original>", and every commit will be "with" you. | |
| Sep 26, 2016 at 14:02 | history | edited | Neil G | CC BY-SA 3.0 |
added 80 characters in body
|
| Aug 15, 2016 at 3:55 | comment | added | neilgee | Each time you do this it adds to the fork a commit ahead of the original | |
| Jul 28, 2016 at 18:32 | comment | added | Tarabass | It works, but they should have used a "rebase fork" and "push" button. In this way it seems so odd to me. Not very intuitive.. | |
| May 30, 2016 at 7:36 | comment | added | runDOSrun | This works but the UI is very clunky. It sometimes suggests the opposite operation as a default, i.e. sending a pull request to the original source. | |
| Apr 19, 2016 at 4:47 | history | edited | Peter Mortensen | CC BY-SA 3.0 |
Copy edited.
|
| Nov 18, 2015 at 12:15 | history | edited | Mr_Green | CC BY-SA 3.0 |
added 35 characters in body
|
| Sep 17, 2015 at 14:08 | comment | added | dirceusemighini | This work, but it didn't bring the new branches to your repo | |
| Aug 5, 2015 at 14:50 | comment | added | Sahar Rabinoviz | @RenniePet If you follow these steps (mainly step 3) you can end up you can end up with This branch is even with <parent>:master. | |
| Jul 21, 2015 at 9:20 | comment | added | Scruffy | @RenniePet In the "This branch is x commit(s) ahead of (original)" message, the x commit(s) refer(s) to a those/that which you made and the upstream forkee has not (yet) merged. The x in the message will increase with every commit you make to that fork. | |
| Jun 18, 2015 at 19:15 | comment | added | Matt Sanders | The merge itself appears to be the 1 commit ahead as soon as you complete the pull request and this is normal. I have noticed that the switching branches no longer works for me. | |
| May 15, 2015 at 22:59 | comment | added | RenniePet | @cartland (or others) - yes, it says "This branch is 1 commit ahead of ..." Is this something to worry about? Is it possible to get rid of that message? | |
| Apr 9, 2015 at 0:08 | comment | added | cartland | April 2015. Works. Thanks. I did get "Switching to base". However, step 6 was "Create pull request" -> enter comment -> "Create pull request". End up with 1 commit ahead of original. | |
| Mar 4, 2015 at 14:05 | comment | added | mluisbrown | Still works (Marchi 2015), all though the "Switching the base" link is no longer there. You have to change the "Base" drop down's so both point to your fork and then you'll get a prompt to "Compare across repos", which will take you to where you want. | |
| Feb 6, 2015 at 11:32 | history | edited | Oren Hizkiya | CC BY-SA 3.0 |
added 1 character in body
|
| Aug 21, 2014 at 18:14 | comment | added | WestCoastProjects | This worked great one time. The second time this process did not work the same way: the "Switching the base" link did not show up. And when I hit "Click to create a pull request" it created a PR on the SOURCE repo. NOT what I wanted.. | |
| Jun 20, 2014 at 8:27 | audit | First posts | |||
| Jun 20, 2014 at 8:27 | |||||
| Jun 15, 2014 at 17:50 | audit | First posts | |||
| Jun 15, 2014 at 17:50 | |||||
| Jun 12, 2014 at 15:16 | audit | First posts | |||
| Jun 12, 2014 at 15:16 | |||||
| May 25, 2014 at 7:31 | history | answered | lobzik | CC BY-SA 3.0 |