fatal: You have not concluded your merge (MERGE_HEAD exists). Please, commit your changes before you merge.
A merge is still in progress — conflicts were resolved (or not) but not committed.
Exact message you may see
You have not concluded your mergeMERGE_HEAD exists
Seen on:
Git
Meaning
Git keeps MERGE_HEAD until you commit or abort.
Common causes
- Merge with conflicts left unfinished
- Forgot to commit after resolving
⚡ Quick fix
- Finish: resolve files, git add, git commit
- Or abort: git merge --abort
Detailed fix by platform
Git
git status && git add -A && git commit
How to diagnose
- State — Conflicted files remaining?
- Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Git
- Git SSL certificate problem fatal: unable to access 'https://…': SSL certificate problem: unable to get local issuer certificate
- kex_exchange_identification kex_exchange_identification: Connection closed by remote host
- Repository not found remote: Repository not found. fatal: repository 'https://github.com/x/y.git/' not found
Other ways to find it
Where this error sits
Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 15 Oct 2026