warning: There are too many unreachable loose objects; run 'git prune' to remove them.
Git’s automatic garbage collection found many unreachable objects and is asking you to prune.
Exact message you may see
too many unreachable loose objectsrun 'git prune'
Seen on:
Git
Meaning
Frequent rebases/amends leave unreachable objects. A gc.log may keep re-triggering the warning.
Common causes
- Lots of history rewriting
- gc.log left from a previous failed auto-gc
⚡ Quick fix
- git prune && git gc
- Delete .git/gc.log if it keeps reappearing
Detailed fix by platform
Git
git gc --prune=now && rm -f .git/gc.log
How to diagnose
- Log — Does .git/gc.log exist?
- 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
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