Yesterday I cherry-picked two commits into my main branch, one of them caused merge conflicts and I resolved them, committed and pushed them to origin. Today I am attempting
Another option: with Git 2.23 (Q3 2019), a git cherry-pick --continue will actually work!
When one step in multi step cherry-pick or revert is reset or committed, the command line prompt script failed to notice the current status, which has been improved.
See commit e981bf7 (01 Jul 2019) by Phillip Wood (phillipwood).
(Merged by Junio C Hamano -- gitster -- in commit 8a4acc5, 19 Jul 2019)
git-prompt: improvecherry-pick/revertdetectionIf the user commits or resets a conflict resolution in the middle of a sequence of cherry-picks or reverts then
CHERRY_PICK_HEAD/REVERT_HEADwill be removed and so in the absence of those files we need to check.git/sequencer/todoto see if there is a cherry-pick or revert in progress.See if a
cherry-pickorrevertis in progress, if the user has committed a conflict resolution with 'git commit' in the middle of a sequence of picks or reverts thenCHERRY_PICK_HEAD/REVERT_HEADwill not exist so we have to read thetodofile.