GitButler ⧓

Commands
>_

but resolve

Resolve conflicts in a commit.

When a commit is in a conflicted state (marked with conflicts during rebase), use this command to enter resolution mode, resolve the conflicts, and finalize.

Workflow

  1. Enter resolution mode: but resolve <commit-id>
  2. Resolve conflicts in your editor (remove conflict markers)
  3. Check remaining conflicts: but resolve status
  4. Finalize resolution: but resolve finish Or cancel: but resolve cancel

Alternatively, resolve with AI in one step: but resolve <commit-id> --ai, or but resolve --ai to resolve all conflicted commits, oldest first.

When in resolution mode, but status will also show that you're resolving conflicts.

Usage: but resolve <COMMAND> [COMMIT] [OPTIONS]

Subcommands

but resolve status

Show the status of conflict resolution, listing remaining conflicted files

Usage: but resolve status

but resolve finish

Finalize conflict resolution and return to workspace mode.

This commits the resolved changes, rebases any commits on top of the resolved commit, and returns to the normal workspace.

Usage: but resolve finish

but resolve cancel

Cancel conflict resolution and return to workspace mode.

This discards all changes made during resolution and restores the workspace to its pre-resolution state.

Usage: but resolve cancel [OPTIONS]

Options:

  • -f, --force — Forcibly remove any changes made

Options

  • --ai — Resolve the conflicts with the configured AI model and apply the result.

With a commit ID this resolves only that commit; without one it resolves all conflicted commits in the workspace, oldest first. Undo the result with but undo.

Last updated on

On this page

Edit on GitHubGive us feedback