Hi Stefan
On 23/02/2024 20:59, Stefan Haller wrote:
On 12.02.24 15:38, Phillip Wood wrote:
Hi Patrick and Stefan
>>
It would certainly be possible to extend the sequencer to do that but
I'm not familiar with why people use "git cherry-pick -m" [1] so I'm
wondering what this would be used for. It would involve a bit of extra
complexity so I think we'd want a compelling reason as to why
cherry-picking merges without maintaining the topology is useful
especially as one can currently do that via "exec git cherry-pick -m ..."
Ok, I suppose the answer will probably not count as a compelling reason.
My reason for wanting this is that lazygit currently implements
cherry-picking in terms of an interactive rebase, rather then calling
git-cherry-pick. And the reason why it does this is that when you
cherry-pick multiple commits, and one of them conflicts, then you get
lazygit's nice visualization of the rebase todo list to show you where
in the sequence you are, what the conflicting commit is, how many are
left etc. It just happens to support this well for
.git/rebase-merge/git-rebase-todo, but not for .git/sequencer/todo.
Thanks for the context. I can see how that is convenient for lazygit
(and makes we think that perhaps we should teach "git status" to show
pending cherry-picks) but I'm afraid I don't think that is a good reason
for adding the ability to pick merges to git rebase.
It probably makes more sense to teach lazygit to visualize the
.git/sequencer/todo file, and then use git cherry-pick.
If lazygit is generating the todo list for the cherry-pick could it
check if the commit is a merge and insert "exec cherry-pick -m ..." for
those commits? The UI could detect that and display something more user
friendly for those lines in the todo list. It is still more work for
lazygit but perhaps less than supporting cherry-picks directly.
Best Wishes
Phillip
