Search the field guide

Search all 29 chapters. Your search stays on this device.

↑ ↓ Move between results Enter Open · Esc Close

Browse chapters

DocsEveryday GitFIELD NOTES / 14

Everyday Git · 1 min read

Conflicts

Preview documentation About this guide ⓘ

GitTrail is in preview: commands and features may change before the first release, and host integrations are still being tested against each live service.

Chapter 14 of 29
On this page

In this chapterResolve conflicts and continue the operation safely.

Two versions. One reviewed result.
Compare both sides
Resolve the conflict
Review and continue

A conflict happens when two branches changed the same lines. A banner shows the merge, rebase or cherry-pick in progress, with Continue, Skip and Abort.

  1. Try Resolve simple conflicts: it fixes every safe case (same change on both sides, only one side changed, spacing only) in all files, and lists what’s left.
  2. Open a file in the conflict editor: choose Accept yours / theirs / both for each block, edit by hand, or switch to the 3-way view (original, yours, theirs above the result).
  3. Smart resolve fixes the safe blocks in the open file.
  4. When the last file is resolved, click Continue.

Reuse resolutions (rerere) remembers how you resolved a conflict and offers it next time. External merge tools (Beyond Compare, Meld, P4Merge, VS Code…) are available from a conflict’s menu.

Check the result

Review the resolved files and the final diff before selecting Continue.

Next step: Review the resulting history before pushing.

Need another approach?Find a fix →