> Unfortunately, the reflog is confusing and hard to use correctly in the case of an interactive rebase with multiple steps. It is hard to figure out exactly ho

> Unfortunately, the reflog is confusing and hard to use correctly in the case of an interactive rebase with multiple steps. It is hard to figure out exactly how far back you need to go in the reflog to get to moment before the rebase started if you want to start over. When you run git reflog after rebasing, you will see lines like the following: 29d82ac HEAD@{6}: rebase -i (finish): returning to refs/heads/your-branch 29d82ac HEAD@{7}: rebase -i (fixup): Commit message 2 4f8e996 HEAD@{8}: rebase -i (pick): Commit message 2 f3a954e HEAD@{9}: rebase -i (pick): Commit message 1 f74b8a5 HEAD@{10}: rebase -i (start): checkout origin/master The line listed after the one that has rebase -i (start) is the commit you were on before you started the rebase. If I screw up a rebase, then I will stash any uncommitted changes and run a git reset --hard to the commit listed below the rebase -i (start) commit I see in the reflog and start the rebase again.