warning: ignoring broken ref refs/remotes/origin/HEAD
A ref file is empty or points to a missing object — usually refs/remotes/origin/HEAD after the default branch changed.
Exact message you may see
ignoring broken ref
Seen on:
Git
Meaning
Harmless but noisy. Re-point origin/HEAD to the current default branch.
Common causes
- Remote default branch renamed (master → main)
- Corrupted/empty ref file
⚡ Quick fix
- git remote set-head origin --auto
- Delete the broken ref file if needed
Detailed fix by platform
Git
git remote set-head origin --auto
How to diagnose
- Ref — Which ref is broken?
- 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
- unfinished merge fatal: You have not concluded your merge (MERGE_HEAD exists). Please, commit your changes before you merge.
- rebase in progress fatal: It seems that there is already a rebase-merge directory, and I wonder if you are in the middle of another rebase.
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 12 Oct 2026