Git New Added 8 September 2026

git: error: pathspec 'x' did not match any file(s) known to git

Git could not resolve the argument as a file, branch or commit. With checkout it usually means the branch exists only on the remote and has not been fetched; with add it means the path is ignored, misspelled, or outside the repository.

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

Quick fix

# Branch: does the remote ref exist locally?
git fetch origin
git branch -a | grep feature/x
git switch feature/x            # creates a tracking branch

# Or fetch just that one
git fetch origin feature/x:feature/x

# File: is it ignored?
git check-ignore -v path/to/file
git add -f path/to/file

# Shallow clones have no other branches at all
git fetch --unshallow

How to diagnose Git errors

Git errors are frightening mostly because the messages describe internal state rather than what to do. The reassuring fact is that almost nothing is lost: git reflog records every position HEAD has held, so a bad rebase, a hard reset or a deleted branch is nearly always recoverable. Before running any destructive command, note the current commit hash.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

Run git status and read it fully. It tells you the current state and usually names the exact command to move forward or abort.
Use git reflog to find any commit you think you have lost, then git reset --hard <hash> or git branch recovery <hash> to get it back.
For a rejected push, run git fetch then git log --oneline HEAD..@{u} to see exactly what is on the remote that you do not have. Prefer --force-with-lease over --force, which refuses to overwrite work you have not seen.
Abort rather than improvise when a merge or rebase goes wrong: git merge --abort, git rebase --abort, git cherry-pick --abort.
For repository corruption, run git fsck --full. If objects are missing, re-cloning and cherry-picking your local work is usually faster and safer than repairing in place.

Tools worth reaching for

git status
git reflog
git fsck --full
git log --graph --oneline --all
git diff --check

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

git-scm.com

Related Git errors

See all 20 Git errors →

Browse other categories

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.