Conversation
|
just merged PR #492 which adds |
|
Haha, well, that makes it easier then. Does my recipe still have a place somewhere? I mean, it allows for more finegrained control (cherry-pick without checkout) and demonstrates how one could use |
|
Best thing would be to show first the higher level interface, and last the advanced usage. |
|
Note that what you're doing here isn't a cherry-pick but a straight merge. Cherry-pick should have the commit's parent as the merge-base. |
|
Ah ok, good to know. But which commit's parent? The cherry's or the basket's? So maybe I'll write a section about how to use the new cherry-pick facility, then what I wrote with the merge-base fixed and possibly a note that you can do other strange things. I don't have time for that right now, but will do it next weekend, I guess. So don't delete the pull request yet. :-) |
|
A cherry-pick means applying a commit's (implicit) diff on top the current commit, so you have to get the cherry and its parents to create the diff. It's not too different from |
|
Hmm, I didn't want to close this. Apparently I messed up things again by force-pushing or something. It would be cool if one could fork one's own repos to try what effects various actions have on pull requests. I could open another account for that… Anyway, I wrote a recipe with both ways of cherry-picking, but when I try this, my repo remains in cherry-picking mode afterwards: Am I failing to do something I should do, but which the docs on |
Add the way that worked for me. Not sure if it is idiomatic.