Resolve in your editor, then:
Shows the commits on your current branch, newest first.
You can do the following rebase operations:
If a rebase produces a merge conflict, a dialog will appear letting you resolve the conflict in your editor and then continue, or abort and return to the original state.
Tip: drag related commits together first, then use squash or fixup.
The Undo Stack holds each past tip of your local branch, sorted chronologically. It begins when the local branch was created.
Each of the following actions moves the current branch and updates the Commit History pane:
The Undo Stack contains only unique modifications to the branch. If a branch is reset to a previous state, the new tip of the branch is not unique and will not be an entry in the Undo Stack. Undo, Redo and Reset actions are non-unique modifications and are not added as new entries to the Undo Stack.
The Undo Stack shows the local branch changes — commits, rebases, resets — regardless of whether they were made inside or outside git-warp.
When you pull or fetch/rebase from the remote, the update to the local branch appears as a single entry in the Undo Stack, not as a series of individual remote commits.
Tip: A failed rebase can be recovered by executing "git rebase --abort".