cherry-pick into the middle of a branch

[durka]

Is your feature request related to a problem? Please describe.

I want to cherry pick a commit from branch A onto branch B, but not at the tip; it doesn't apply there. I want to paste it further back in the branch.

Describe the solution you'd like

Maybe shift-V should do this, if the cursor isn't at the top of the commit pane? But that's a breaking change, so maybe a new keybinding is needed.

The implementation is: start an interactive rebase, insert pick line(s) with the commit(s) to be cherry-picked, then run it. Or alternatively: roll back the branch to the insertion point, perform the cherry-pick(s), then cherry-pick the subsequent orphaned commits.

Describe alternatives you've considered

I tried starting an interactive rebase with i and then pasting with shift-V, but that just generated a bunch of errors.

I ended up doing it on the CLI by doing git rebase -i and then pasting in pick lines to the todo file.

[stefanhaller]

Doing it manually in the middle of an interactive rebase is the way to do this. Press 'e' on the commit after which you want to insert the commit (or 'i' if you want to paste at the beginning of the branch), then paste as normal there. This works well, I do it often.

I don't think this needs an extra key binding, I find this pretty convenient and intuitive.

If this doesn't work for you, you'll have to be more specific about what those "bunch of errors" were.

[durka]

Yep, that works. I just couldn't figure out how to do it.

…

On Sat, Jan 10, 2026, 2:34 AM Stefan Haller ***@***.***> wrote: *stefanhaller* left a comment (jesseduffield/lazygit#5191) <#5191 (comment)> Doing it manually in the middle of an interactive rebase is the way to do this. Press 'e' on the commit after which you want to insert the commit (or 'i' if you want to paste at the beginning of the branch), then paste as normal there. This works well, I do it often. I don't think this needs an extra key binding, I find this pretty convenient and intuitive. If this doesn't work for you, you'll have to be more specific about what those "bunch of errors" were. — Reply to this email directly, view it on GitHub <#5191 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAALPHZ7AAFSMROJJZDHMKL4GCTRHAVCNFSM6AAAAACRHNURRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZSGEYDGNZXHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>