I can see if that's possible, but .. multi-change pull requests would be squashed into a single change instead of merge (which is actually a bigger alternation)
That's not what I mean. We'd better not squash multiple commits into one for merge. What I'm saying is: better not introduce the extra merge commit; like commit 4a620c436da, there's no single line of code.
0416c247eca has 05871a1cdc7 as it’s second parent
But this pull request only has one commit: google/gvisor#1176
It might also just be a case of merges being confusing: do things make more sense if you just do “git log —no-merges” ?
Yep, I can do that.
I will see if we can get rid of the merge commit and do an automatic rebase for the single commit case
Great, that'll save some confusion. Thanks!