Reverting a commit from Log

Reverting applies a commit's reverse changes to your index and working tree. It leaves the current commit and branch history intact until you create a new commit with those changes.

Select a non-root commit in Log Messages.
Choose Revert change by this commit from its context menu. For a merge, choose the parent against which the changes should be reversed.
Confirm Yes to apply the reverse changes. No is the default and keeps the repository unchanged.
Review the result. Commit opens the Commit workflow; OK leaves the changes available for review and committing later.

For a merge, Parent 1 is usually the branch on which the merge was made. Choosing it reverses the changes introduced relative to that parent. Each submenu item shows the parent commit's title and abbreviated hash to help you choose. Check those values rather than assuming which branch a parent represents.

The single-row command is unavailable for root commits and stash rows. Revert also requires a working tree without an active merge. If Git reports conflicts, resolve them before finishing the operation. The app leaves conflict state available; it does not silently roll back changes. Unrelated changes can remain in your working tree, but overlapping edits may prevent Git from applying the reverse patch.

Reverting several selected commits

Select the rows and choose Revert changes by these commits. Revert processes them in displayed order and leaves the inverse changes uncommitted. A root commit can be included in this batch. A selected working-tree row contributes to the progress count but has no commit to reverse.

A batch does not choose merge parents. Merge commits, including stash commits, therefore offer Skip or Abort when a mainline is required. Use the single-commit parent submenu to reverse a particular merge against its chosen parent. Skip proceeds to the next row; Abort stops further attempts. Earlier successful changes and their accumulated commit messages remain available for review. Cancelling also retains changes already applied; inspect the working tree before another operation.

See Log Revert parity for remaining workflows and verification. Displayed macOS screenshots for this workflow are still pending.