Repository navigation
[cherry-picker] [idea 馃挕] Extend backport sources聽#13
Description
Activity
- changed the title
[-][cherry-picker] [idea :bulb:] Extend backport sources[/-][+][cherry-picker] [idea :bulb: ] Extend backport sources[/+]on Jun 22, 2018 - changed the title
[-][cherry-picker] [idea :bulb: ] Extend backport sources[/-][+][cherry-picker] [idea 馃挕] Extend backport sources[/+]on Jun 22, 2018 Not sure if this is related, but I would really love the ability to backport merge requests or a range of commits. Either pass
cherry_pickera merge commit SHA and have it do the right thing (-m 1maybe?), or have it accept a range likegit cherry-pickdoes with[SHA]..[SHA].Actually, it looks like ranges work (I was just getting hit by a merge conflict and the
--continuedidn't to the right thing after resolving). It would still be handy to be able to pass in a merge commit, though.I think it wouldn't be hard to detect whether some commit is a merge. OTOH it could be harder to figure out whether to pass
-m1or-m2(though could probably be done by inspecting the parents and checking if it belongs to the default branch).Right. I wasn't sure about the value for
-m. That would take a bit more work and I don't really know how complicated that could get.
I think with https://help.github.com/articles/checking-out-pull-requests-locally/ and https://gist.github.com/piscisaureus/3342247#gistcomment-1566295 cherry-picker could do better and even backport rebase merges and normal merge commits.