fatal: refusing to fetch into branch 'refs/heads/main' checked out at ... (Git) — how to fix
fatal: refusing to fetch into branch 'refs/heads/main' checked out at '/home/me/project'
fatal: Refusing to fetch into current branch refs/heads/main of non-bare repository
Quick fix: Don't fetch into the current branch. Use git pull origin main (fetch + merge), or git fetch origin then git merge origin/main. If you really want to update a local branch with fetch, switch away from it first: git switch other && git fetch origin main:main.
What it means
git fetch origin main:main means "download main from origin and write it into my local branch main". If main is the branch you have checked out (in this worktree or another worktree), updating its ref would leave your index and working files out of sync with HEAD. Git refuses rather than silently corrupt your state.
Newer Git phrases it as "refusing to fetch into branch ... checked out at
Fix 1: use pull or fetch + merge
Normally you don't want to write into the local branch with fetch at all. Fetch updates remote-tracking refs (origin/main); then integrate:
git fetch origin
git merge origin/main # or: git rebase origin/main
Or in one step:
git pull origin main
Fix 2: update a branch you are NOT on
The src:dst fetch form is handy for fast-forwarding another local branch without checking it out:
git switch feature
git fetch origin main:main # fast-forwards local main, works now
It only succeeds if it's a fast-forward; add + (+main:main) to force, which discards local commits on that branch.
Fix 3: the branch is checked out in another worktree
git worktree list
If main is checked out in another worktree, either run git pull inside that worktree, switch that worktree to another branch, or remove it:
git worktree remove ../project-main
Fix 4: scripts and CI with a bad refspec
A config like this triggers it on every plain git fetch:
[remote "origin"]
fetch = +refs/heads/*:refs/heads/*
That maps remote branches straight onto local ones — only correct for bare mirrors. Restore the default:
git config remote.origin.fetch "+refs/heads/*:refs/remotes/origin/*"
Fix 5: you know what you're doing
git fetch --update-head-ok origin main:main bypasses the check (used internally by git pull). Afterwards your working tree doesn't match HEAD; run git reset --hard HEAD only if you have no uncommitted changes worth keeping. Fix 1 is almost always the better choice.
Related
In a non-bare repo the same protection exists on the push side: pushing to a checked-out branch fails with "refusing to update checked out branch". Push to a bare repo instead, or set receive.denyCurrentBranch updateInstead on the server repo.
Last updated 2026-11-09.