I would like to clone a repository from GitHub. The problem is I don't want the main branch; I want the version in this unapproved pull request.
Is it possible for me to clone the pull request version instead of the main repository?
13 Answers
The easiest way to do that is like this:
git fetch origin pull/<pr_number>/head:<local_branch_name> git switch <local_branch_name> You will now be on a new branch that is on the state of the pull request.
You might want to set up an alias by running
git config --global alias.pr '!f() { git fetch -fu ${2:-origin} refs/pull/$1/head:pr/$1 && git checkout pr/$1; }; f' Now you can checkout any PR by running git pr <pr_number>, or git pr <pr_number> <remote> if your github remote is not named origin.
9 Comments
matt---
I found myself referencing this SO answer often, so I stuck this into my
.gitconfig file under [alias]: pr = "!f() { git fetch $1 pull/$2/head:pull_$2; git co pull_$2; }; f". That way I just type git pr upstream 62 and next thing I know, I am on a new branch of PR #62 from upstream! If you always use origin you could hardcode it instead of the $1, but that switches around for me.
giraffesyo
@matt that assumes you have an alias for checkout named
co
nponeccop
How do I pull it when commits are added?
--set-upstream-to doesn't seem to work. Is there a better way than git fetch ... && git reset --hard FETCH_HEAD?
Jim Klimov
Thanks to your posts. My twist on this is the following
[alias]: pr = "!f() { if [ $# -gt 1 ] ; then REM="$1"; NUM="$2"; else REM="upstream"; NUM="$1"; fi; git fetch "$REM" "pull/${NUM}/head:pull_${NUM}"; git checkout "pull_${NUM}"; }; f" which allows to git pr 123 and git pr somefork 456 in a bit more natural argument order than having the fork remote name in the end, as per original port. Matter of taste :) |
You can clone the branch you want by using the -b option and for pull request:
git clone https://github.com/user_name/repo_name.git -b feature/pull_request_name dir_name In your case, the branch you want to clone is the source branch of the pull request (feature/mongoose-support):
git clone https://github.com/berstend/frappe.git -b feature/mongoose-support ./mongoose-support 
Comments
git fetch origin refs/pull/PR_NUMBER/head:NEW_LOCAL_BRANCH eg:
git fetch origin pull/611/head:pull_611 git checkout pull_611 Make changes, commit them, PUSH and open new PR from your fork on GitHub
1 Comment
erginduran
how can i merge this branches locally? i just cloned and fetched an unmerged pull request as above you did.And tried checkout branchname.But no changes appear in my IDE/text editor.
git clone git://github.com/dweldon/frappe cd frappe git pull origin pull/2/head How can I fetch an unmerged pull request for a branch I don't own?
1 Comment
Beni Cherniavsky-Paskin
Note
git pull creates a merge into current branch; usually for a PR you'd want to just git fetch to get original author's code (it's then accessible as FETCH_HEAD). If you do want a merge, it's worth also mentioning pull/2/merge (instead of pull/2/head) — this makes GitHub give you the exact merge commit that would happen if you clicked [Merge] button now.You could follow the directions in this gist to be able to check out the remote directly without having to figure out their repository and branch.
Example usage
For one of my projects (github3.py) I have the following in my github3.py/.git/config
[remote "github"] fetch = +refs/heads/*:refs/remotes/github/* fetch = +refs/pull/*/head:refs/remotes/github/pr/* url = [email protected]:sigmavirus24/github3.py The first line is what is standard for every remote with the exception that github is replaced by the remote's name. What this means is that remote heads (or the heads of branches on that server) are "mapped" to local remotes prefixed by github/. So if I did git fetch github and had a branch on GitHub that wasn't already noticed locally on my machine, it would download the branch and I could switch to it like so: git checkout -t github/branch_name.
The second line does the same thing, but it does it for pull requests instead of standard git branches. That's why you see refs/pull/*/head. It fetches the head of each pull request on GitHub and maps it to github/pr/#. So then if someone sends a pull request and it is numbered 62 (for example), you would do:
git fetch github git checkout -t github/pr/62 And then you would be on a local branch called pr/62 (assuming it didn't already exist). It's nice and means you don't have to keep track of other people's remotes or branches.
answered Feb 19, 2013 at 0:45
Ian Stapleton Cordasco
29.2k4 gold badges73 silver badges73 bronze badges
6 Comments
Ian Stapleton Cordasco
Why not? It explains exactly how to do this in a convenient and efficient way.
Fresheyeball
Because I am a noob, and that document is difficult to understand. I never would have gotten from "not getting it" to
git clone https://github.com/berstend/frappe.git -b feature/mongoose-support /my_clone from the gist document.Ian Stapleton Cordasco
What the gist document does is add an extra set of information (refs or references) to fetch from GitHub. When you do
git fetch github you can then do git co -t github/pr/#. This prevents you from having to copy and paste the remote URL, figure out the branch name, etc. You then get well-named, concise and accurate branch names without the extra hassle. But I understand it may seem overwhelming.Fresheyeball
Oh nice. I did not know this +1! Can you give me a fully qualified example?
Petr Kozelka
@sigmavirus24 thanks a lot for the information; I wonder if similar trick exists for bitbucket?
|
When a user submits a pull request, they are asking for some changes to be merged from a branch on their clone of a fork back to another user's repository.
The changes you want can be got from the source of the pull request. To do this, clone the user's repository (git://github.com/berstend/frappe.git), and then check out the branch he created the pull request from (feature/mongoose-support).
Comments
With Github's official new command line interface:
gh repo clone org/repo cd repo gh pr checkout 44 where 44 is the PR number, but can also be the branch name.
See additional details and options and installation instructions.
Comments
To pull PR to your current branch use:
git pull origin pull/418/head
Here pull/{no. of PR}/head
Comments
For me, it was as simple as
git fetch origin pull/4/head Where 4 was found here:
1 Comment
Soylent Graham
Doesn't work with
git cloneBitBucket convention for listing and fetching PRs:
git ls-remote origin 'refs/pull-requests/*' git fetch origin refs/pull-requests/998/from:local-branch-name Full article here: https://www.atlassian.com/git/articles/pull-request-proficiency-fetching-abilities-unlocked
Comments
After installing git-extras
(cd /tmp && git clone --depth 1 https://github.com/tj/git-extras.git && cd git-extras && sudo make install) You can simply use git pr
$ git pr 62 [remote] 
Comments
That pull request shows the commits from that person's fork so you can see that he is pushing his changes from feature/mongoose-support branch.
You can clone his repository and checkout that branch
Comments
The accepted answer with "-b" option didn't work for me, so this is what I've ended up with. After pull request is created in Github, you'll be taken to the page where you can see something like below, where 'ogryb' is my user name and 'patch-1' is an automatically generated name assigned to it.
All you need to do now is to click on that highlighted name on the right, which will take you to a page with the following link:
Click on the right side of the green "Code" button to see a nice personalized git link that can be used for cloning or for adding more changes to the existing pull request.
1 Comment
ijuneja
This won't be good for cloning someone else's pull request if they have since made other changes to their fork which the cloner does not want.
clonebut forfetchsee: stackoverflow.com/questions/6743514/…