GitGlow 2.0 guide

Resolve Git conflicts

Resolve merge, rebase, cherry-pick, and revert conflicts with correctly labelled inputs.

Reviewed for 2.0Updated September 13, 2026
On this page

What this helps you do

Resolve merge, rebase, cherry-pick, and revert conflicts with correctly labelled inputs.

Find it in GitGlow

An active Git operation opens the operation banner and conflict resolver in Changes.

Before you start

Resolution, Continue, and Abort remain available on Free so an in-progress operation cannot trap the checkout.

Steps

  1. Select an unresolved path and inspect Current, Incoming, and optional Base content.
  2. Choose Use left, Use right, Use both, or edit the Result.
  3. Review Save resolution, repeat for remaining paths, then choose Continue operation.

Expected result

Resolved content is written only after revalidation, staged, and protected by a recovery copy.

Controls

Continue operationoperation.continue

Continues the active Git operation when all paths are resolved.

Screen
Operation banner
Available
Free continuation
Open workflow guide →
Abort operationoperation.abort

Asks Git to abort the active operation.

Screen
Operation banner
Available
Free continuation
Open workflow guide →
Use leftconflict.left

Copies the labelled left input into Result.

Screen
Conflict resolver
Available
Free continuation
Open workflow guide →
Use rightconflict.right

Copies the labelled right input into Result.

Screen
Conflict resolver
Available
Free continuation
Open workflow guide →
Use bothconflict.both

Combines both inputs in Result for review.

Screen
Conflict resolver
Available
Free continuation
Open workflow guide →
Save resolutionconflict.save

Writes and stages the reviewed result after revalidation.

Screen
Conflict resolver
Available
Free continuation
Open workflow guide →

Recovery

If the workflow cannot continue

For binary or modify/delete conflicts, use the offered complete-side or delete choice. Abort remains available when Git supports it.