Comment by justinmk | Hacker News Reader

Comment by justinmk | Hacker News Reader

Parent Full thread

> Don't use the merge button, just add the requester's repo as a remote to yours

Actually, you don't need to do that. GitHub provides a special pulls remote "namespace" on the upstream repo, so you can add it as a fetch pattern to your .git/config like so:

    [remote "upstream"]
      url = https://github.com/neovim/neovim.git
      fetch = +refs/heads/*:refs/remotes/upstream/*
      fetch = +refs/pull/*/head:refs/pull/upstream/*

Then when you `git fetch --all`, you will have ALL pull requests available in your local repo in the local pull/ namespace. To check out PR #42:

    git checkout -b foo refs/pull/upstream/42

Wow you are my new favorite person. What I was going to say was that the GP was correct in that it just took a bit more work on the maintainers part to keep the history clean, but even that is unnecessary apparently :-)

Good tip.

It's interesting that other systems has a nicer implementation for it.

In Phabricator, it's:

  $ arc patch D12345

and it checks out revision 12345 into an appropriately named branch.

Yes! I've been wanting to do this and didn't know it was this easy.

That is great, and i thank you for bringing that to my, and everyone else's attention! :)

This is... amazing. Thank you so much.

is this documented somewhere on github?

Yeah, I have to google the precise path every time I need it: https://help.github.com/articles/checking-out-pull-requests-...

WOW, this has been missing from my life for way too long!

Thank you :D

You rock!

Reply on news.ycombinator.com