Git unmerged-paths You have unresolved file conflicts preventing Git from completing the current operation.
Reviewed for reference consistency: April 11, 2026
Code is Safe
SECUREGit has paused the operation to protect your code. No data has been lost or corrupted.
What To Know
Where Did It Fail?
Commands That Trigger This
Technical Background
This message is a direct consequence of a previous operation (like a pull or merge) failing to complete.
It acts as a safeguard to prevent half-merged, broken code from being permanently recorded into the repository history.
Underlying Causes
Frequently Asked Questions
Git reads the index. If a file has multiple stages recorded (base, local, remote) instead of a single resolved version, Git considers it unmerged.
Related Git States
Git paused the merge because it cannot automatically resolve overlapping changes.
Git aborted the merge to protect uncommitted changes in your working directory.
You tried to run a Git command while a previous rebase operation is still paused.