• Fast Forward Your Fork

    schacon 12 Dec 2008

    Since forking a repository is so easy on GitHub, a number of people tend to do it thinking they want to play with the source, but then never actually push back into their fork. Meanwhile, development continues on the main branch, and it’s a little annoying to have to add them as a remote and merge in order to get back up to date. So, we’ve added a new button to your repository details that will show up if you forked a project, didn’t push to it, and the source repo has moved on:

    If you click on ‘Fast Forward’, it will move all your branches up to wherever the repository you originally forked from now is. Now all of those of you who forked Rails months ago and never did anything with it and are thinking of trying again, go forth and Fast Forward.

  • Comments

    davidwparker Fri Dec 12 18:50:26 -0800 2008

    That’s a nice feature for those of us who dream of helping out and get side-tracked. Awesome.

    broney Fri Dec 12 19:27:06 -0800 2008

    I can’t see it on my repo.

    schacon Sat Dec 13 10:24:44 -0800 2008

    It will only show up if :

    • you have forked a project
    • you have never pushed to your fork
    • the parent project has moved forward

    If that is true and you still don’t see it, let me know the name of the project and I’ll check it out.

    broney Sun Dec 14 22:58:00 -0800 2008

    I’m assuming those are all and conditions.

    Is there any way to fast forward to the latest commit even if you have pushed?

    awendt Mon Dec 15 00:45:50 -0800 2008

    What about people who’d like to rebase their changes on the original repository’s HEAD?

    I’d like to do that with my fork…

    ymendel Wed Dec 17 18:53:22 -0800 2008

    I second bdude’s desire to see this even if you have pushed. If it’s a clean fast-forward, I’d love to have the button.

    Of course, it’s more work to check if there’s been a push.

    grempe Fri Dec 19 22:03:02 -0800 2008

    And a nice to have would be that even if I pushed to my fork, but only made changes on another branch (e.g. a ‘bugfixes’ branch) without modifying master at all I should be able to fast forward master.

    When I contribute a patch to another project I usually do those changes on a branch on my fork so that I don’t pollute master with my commit which the owner of the repo may or may not choose to merge into the parent repo.

    polarapfel Sun Dec 21 13:52:02 -0800 2008

    Worked great for me. Good job. github rocks!!

    peterjc Mon Mar 23 07:46:08 -0700 2009

    Can you include this information on the git guides please?

    Please log in to comment.