[FIXED] Error 'fatal: cannot lock ref' in Git

The error error: cannot lock ref 'refs/remotes/origin/main': is at ... but expected ... or fatal: cannot lock ref occurs during git pull, git fetch, or git checkout when local Git reference pointers become corrupted from abrupt process terminations or case-sensitivity branch conflicts.

🚀 Step-by-Step Fixes

Step 1: Prune Stale Remote References

In most scenarios, this happens when branches deleted on GitHub/GitLab still exist in your local tracking cache:

git remote prune origin

Now retry your fetch command:

git fetch origin

Step 2: Remove Stale Lock Files

If a git operation was abruptly killed (power loss or terminal kill), Git leaves behind temporary safety lock files:

# Remove specific lock file
rm -f .git/refs/remotes/origin/main.lock

# Purge any stale lock files in refs directory:
find .git/refs -name "*.lock" -type f -delete

Step 3: Resolve Case-Sensitivity Branch Collisions

If two remote branches differ only by case (e.g., Feature and feature), case-insensitive filesystems (Windows/macOS) fail to create distinct reference files.

Repack reference files into a single packed-refs file:

git pack-refs --all --prune