1001Ferramentas
🔱 Dev

Git Merge Conflict Resolver

Splits a file with Git conflict markers into ours and theirs versions, lets you pick a side per hunk and outputs the resolved file.

Seeing both sides before you pick one

The merge hit a conflict and the file came back with those angle-bracket markers sitting in the middle of your code. In the editor, with broken indentation and both versions jammed together, it is easy to delete the wrong line and only find out at code review. Paste the whole file here and each conflict appears on its own, with each branch's side in a separate block and the line numbers involved.

For every conflict you choose what stays: your side, the incoming side, both in sequence, or, when the merge used diff3, the base version the divergence came from. The tool reassembles the file with your choices applied and hands back a result ready to paste, leaving the rest of the file untouched and keeping the original line ending, whether LF or CRLF.

The summary flags the cases usually resolved on autopilot: conflicts where both sides are identical, and those where one side is empty, typical of reordered imports. Orphan markers left by a botched hand edit show up as a warning rather than breaking the parse. The pasted file never leaves the browser, so it is safe to use with work code.

Frequently asked questions

What do HEAD and the name after the arrows mean?
HEAD is the state of your branch at merge time, and the name on the right is the branch being merged in. The tool shows these labels exactly as they appear in the file.
Does it resolve the conflict for me?
No. It separates, explains and reassembles the file according to the choice you make for each block. Deciding which version of the code is correct remains human work.
Does it handle merges made in diff3 mode?
Yes. When the file carries the base section, between vertical bars, it is shown as a third block and becomes another resolution option.

Related Tools