It's just: git fetch origin pull/ID/head:BRANCHNAME git checkout BRANCHNAME
Edit: I see that MaikuMori[2] posted the same information just before me; ah well.
[1]: https://help.github.com/articles/checking-out-pull-requests-...
Agreed, and in my experience, every major open source project I'm familiar with requires pull requests to feature branches. In fact, most small projects use the same workflow.
Is this not the case with most open source projects?
There are a lot of small, one-off, often very useful utilities that people are now sharing with each other via Github (I'm guilty/a participant in this phenomenon), and many noble users of these utilities want to help, contribute, and send PRs... a non-negligible number of them new to Git.
So, is it more of a PITA to set up a feature branch for a single python script and instruct users in your CONTRIBUTING file to 'make sure they submit PRs to branch XYZ!' or just deal with the odd occasional PR to master? Folks new to Git will probably just send a PR to master anyway (I believe OP addresses the 'new user' issue as well, having to explain Git commands to users in comments on a PR)
That all being said, I still typically follow the workflow shadowmint outlines above.
In general I'd just encourage maintainers to try the `git am` flow, especially on small to medium complexity contributions where it looks mostly ready to go and you don't want to do another week of ping-pong with the contributor just to get a variable renamed or some whitespace fixed.
As I tell my kids, "Just try one bite of <food I find delicious>. If you don't like it, that's cool, then it's more for me!" :-)
I haven't learned git yet so maybe my assumption that the original PR is on a branch/repo clone to which you can submit a PR is incorrect?
Bob requests that Alice merge bob/bob-feature into alice/master.
Alice requests that Bob merge alice/fix-bob-to-conform-to-pep8 into bob/bob-feature.
Bob merges that into bob/bob-feature, and Bob's PR into Alice's repo is now auto-updated to reflect the changes that he merged into his branch.
Alice is now satisfied, and merges bob/bob-feature with alice/master.
The issue described by the author is definitely more of a workflow problem than a technology or service problem.
...but it doesn't so you have to:
Which is entirely true; it is annoying.The simple solution, though, is to require pull requests to come in a feature branch, and flat out reject any that target master. /shrug