Reviewed for reference consistency: April 11, 2026
Data Loss Risk
HIGH RISKGit stopped to prevent overriding unsaved work. Do not force commands without stashing or committing first.
What To Know
Where Did It Fail?
Commands That Trigger This
Technical Background
Git prioritizes data safety above all else. Because untracked files are not stored in Git's history, they cannot be recovered if overwritten.
By aborting the merge, Git forces you to either track, rename, or delete the file manually before proceeding.
Underlying Causes
Frequently Asked Questions
Git is protecting a file that exists only on your disk and is not yet recoverable from repository history. That is why it stops before the merge writes a tracked file at the same path.
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.
Git prevented a branch switch because it would overwrite unsaved changes in your working directory.