fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
The repository has no commits yet (or the ref doesn’t exist), so HEAD can’t be resolved.
ambiguous argument 'HEAD'unknown revision or path not in the working tree Meaning
Fresh repositories, shallow CI clones, or typos in branch names. Tools that run git describe/rev-parse HEAD fail before the first commit.
Common causes
- No commits yet
- Typo in a revision name
- Shallow clone missing the referenced commit
⚡ Quick fix
- Make an initial commit
- Fetch more history (fetch-depth: 0)
- Use -- to separate paths from revisions
Detailed fix by platform
Git
git commit --allow-empty -m "Initial commit"
How to diagnose
- Commits — git log works?
- 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.
Report a correction or suggest an improvement
Last updated 13 Oct 2026