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 is strictly designed to never destroy uncommitted work without explicit force flags.
When Git detects that an incoming merge touches the exact same file you are currently editing, it halts entirely before altering your local disk.
The key point is that Git wants those local edits preserved in a safer state before it attempts to overlay incoming tracked content.
Underlying Causes
Frequently Asked Questions
Merge conflicts require both sets of changes to be committed to the repository. Uncommitted working directory changes are not safely stored yet, so Git aborts to protect them.
Related Git States
Git paused the merge because it cannot automatically resolve overlapping changes.
Git prevented a branch switch because it would overwrite unsaved changes in your working directory.
Git aborted the merge because it would overwrite untracked files in your working directory.
You have unresolved file conflicts preventing Git from completing the current operation.