Menu
Engineering

Coding & Git

Merge conflict

Also called conflict.

In plain English

A merge conflict happens when Git cannot automatically reconcile competing changes.

Example

One branch edits a page title while another branch deletes that page. Git cannot pick a result on its own, so a person decides what the finished files should be.

Why it matters

Git stops and asks a person to choose the finished result. A conflict is not only two edits to the same line. It can also happen when one change edits a file that another change deletes, or when nearby edits do not combine cleanly.

The site in a browser does not change until someone resolves the conflict, records the result, and deploys.

Common confusion

Conflict markers in a file are a pause in combining history. They are not, by themselves, a broken public site.

Sources

Updated September 30, 2026.

Cookie preferences