Chris's Wiki :: blog/programming/GithubPRTestingWorkflow Commentshttps://utcc.utoronto.ca/~cks/space/blog/programming/GithubPRTestingWorkflow?atomcommentsDWiki2015-08-02T13:34:20ZRecent comments in Chris's Wiki :: blog/programming/GithubPRTestingWorkflow.By Aristotle Pagaltzis on /blog/programming/GithubPRTestingWorkflowtag:CSpace:blog/programming/GithubPRTestingWorkflow:c33e82db49bbe5361862cd9a2a1938e3d6a61df0Aristotle Pagaltzishttp://plasmasturm.org/<div class="wikitext"><p>When you come to that bridge, <a href="http://stackoverflow.com/q/4084868">here’s how you get to the other side</a>.</p>
</div>2015-08-02T13:34:20ZBy Christian Neukirchen on /blog/programming/GithubPRTestingWorkflowtag:CSpace:blog/programming/GithubPRTestingWorkflow:231f22a9995bace1c316ea72e78efb09e1542ac6Christian Neukirchenhttp://chneukirchen.org/<div class="wikitext"><p>In my experience, for just quickly testing the PR, nothing beats something like</p>
<pre>
curl https://github.com/$user/$pkg/pull/$id.patch | git am -
</pre>
<p>Which will just dump the commits on top of whatever you have currently.
Use ORIG_HEAD to revert again.</p>
<p>(Made a bit more convenient and possible to pass -i in <a href="http://chneukirchen.org/dotfiles/bin/git-merge-pr">http://chneukirchen.org/dotfiles/bin/git-merge-pr</a>)</p>
</div>2015-07-30T11:57:37Z