====== HOWTO: Test and merge github pull-requests locally ======

Today, another [[https://github.com/apollo-ng/picoReflow/pull/7|pull-request]] flew in, enhancing the [[mission:resources:picoreflow]] software stack with MAX6675 compatibility. Git and github are great tools for open collaboration but it takes some time to get used to them. Of course, the github auto-merge feature is great and works pretty reliable, but I still prefer to review and test PR's locally on the commandline, before actually merging them. 

{{ :mission:log:2014:12:19:github-pull-request-auto-merge-command-line.png |}}

Github also offers some command line foo for this, as you can see in the screenshot above but I'd like to use this opportunity to share another way how to test, handle and merge github pull requests even more easily and comfortably, in case you're new to git/github and don't know about this yet in a real-world, step-by-step example.

===== Adding pull refs to your .git/config =====

Just go into the directory where you store the git repo you have received a pull request for and open .git/config in an editor. You'll find a section that looks like this (with your repo names of course).

<code>
[remote "origin"]
     url = git@github.com:apollo-ng/picoReflow.git
     fetch = +refs/heads/*:refs/remotes/origin/*
</code>

We just have to add another fetch target so our git knows where to fetch pr's from github: 

**fetch = +refs/pull/*/head:refs/remotes/origin/pr/***

Now the section should look like this.

<code>
[remote "origin"]
     url = git@github.com:apollo-ng/picoReflow.git
     fetch = +refs/heads/*:refs/remotes/origin/*
     fetch = +refs/pull/*/head:refs/remotes/origin/pr/*
</code>

This has to be done only once per project/repo. Afterwards you can just start with Step 1:

===== Simple 4-Step Fetch/Test/Merge/Push =====

==== Step 1: Fetch & checkout the pull request ====

When receiving a new pull request on github, you'll get a notification with the pull request's id, like this: 

https://github.com/apollo-ng/picoReflow/pull/7. 

Now we just have to fetch from origin to see if it pops up:
     
<code>
 $ git fetch origin
From github.com:apollo-ng/picoReflow
 * [new ref]         refs/pull/7/head -> origin/pr/7
</code>

Good, PR #7 is here and we can just switch over to it (checkout):

<code>
$ git checkout pr/7
Branch pr/7 set up to track remote branch pr/7 from origin.
Switched to a new branch 'pr/7'
</code>

==== Step 2: Do your worst (Testing) ====

Review and test the new code.

==== Step 3: Merge the pull-request ====

Once testing is finished and everything seems to be in order, we merge the pull request into the branch we want, in this case the master branch, so let's checkout master:

<code>
$ git checkout master
</code>

Finally we merge the pull request into the master branch and since github already told us that it could merge the PR automatically, we don't expect to be confronted with any merge conflicts:

<code>
$ git merge pr/7
Merge made by the 'recursive' strategy.
 config.py.EXAMPLE |   3 +++
 lib/max6675.py    | 125 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 lib/oven.py       |  20 ++++++++++++++++++--
 3 files changed, 146 insertions(+), 2 deletions(-)
 create mode 100644 lib/max6675.py
</code>

==== Step 4: Push ====

Now we just have to push it back to github which will automagically mark the pull request as closed/merged and notify the pull request initiator.

<code>
$ git push
</code>

Done. Easy, right?


{{tag>git github merge test pull-request howto}}

{{keywords>Apollo-NG apollo next generation hackerspace hacker space development makerspace fablab diy community open-resource open resource mobile hackbus git github merge test pull-request howto ref pull}}

~~DISCUSSION~~