Error map
untracked files overwritten error: The following untracked working tree files would be overwritten by checkout/merge
Git · layer 7, Build & delivery
Centre: this error. First ring: errors it is linked with (7). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (7)
error: Your local changes to the following files would be overwritten by merge
git pull/merge would modify files you’ve changed but not committed.
error: cannot lock ref 'refs/remotes/origin/x': is at … but expected … / unable to update local ref
Git couldn’t update a reference — stale remote-tracking refs, case-only branch name clashes, or a leftover lock file.
error: cannot pull with rebase: You have unstaged changes. Please commit or stash them.
A rebase (or pull --rebase) needs a clean working tree.
fatal: a branch named 'x' already exists
You tried to create a branch whose name is already taken locally.
fatal: Authentication failed for 'https://github.com/x/y.git/'
HTTPS authentication to the Git host failed — wrong or expired credentials, or a password used where a token is required.
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.
error: Your local changes to the following files would be overwritten by checkout
Switching branches would discard uncommitted changes in files that differ between branches.
Two steps away (19)
Git: CONFLICT (content): Merge conflict in file — Automatic merge failed
Both branches changed the same lines; Git needs you to choose the final content before completing the merge/rebase.
fatal: Not possible to fast-forward, aborting.
pull is configured to fast-forward only, but your branch and the remote have diverged.
fatal: You have not concluded your merge (MERGE_HEAD exists). Please, commit your changes before you merge.
A merge is still in progress — conflicts were resolved (or not) but not committed.
error: remote origin already exists.
A remote named origin is already configured.
remote: Repository not found. fatal: repository 'https://github.com/x/y.git/' not found
GitHub/GitLab says the repository doesn’t exist — or you lack access to a private repo.
fatal: No url found for submodule path 'x' in .gitmodules
A submodule entry exists in the index but its URL is missing from .gitmodules.
fatal: It seems that there is already a rebase-merge directory, and I wonder if you are in the middle of another rebase.
A previous rebase is still in progress (or was interrupted).
Error downloading object: x: Smudge error / This repository is over its data quota
Git LFS couldn’t download a large file — missing LFS install, auth problems, or the LFS bandwidth/storage quota is exhausted.
error: commit x is a merge but no -m option was given.
git revert or cherry-pick on a merge commit needs to know which parent is the mainline.
Git: ! [rejected] … (fetch first) — error: failed to push some refs
The remote branch has commits you don’t have locally, so Git refuses to overwrite them. Pull (merge or rebase) first, then push.
You are in 'detached HEAD' state.
HEAD points at a commit instead of a branch, so new commits won’t belong to any branch.
error: pathspec 'x' did not match any file(s) known to git
Git couldn’t find the file or branch name you referenced.
Git: Permission denied (publickey). fatal: Could not read from remote repository.
SSH authentication to GitHub/GitLab/Bitbucket failed — no key, wrong key, or the key isn’t added to your account.
Azure AD (Entra ID): AADSTS700016 Application not found in the directory
The client ID in your sign-in request doesn’t exist in the tenant you’re authenticating against.
HTTP 401 Unauthorized
The request has no valid authentication credentials — you need to log in or send a valid token.
fatal: Unable to create '.git/index.lock': File exists. Another git process seems to be running in this repository
A lock file from another (or crashed) Git process blocks this command.
fatal: Not a valid object name: 'main'.
The branch or commit doesn’t exist yet — typically in a new repo before the first commit.
fatal: couldn't find remote ref main
The branch you tried to pull/fetch doesn’t exist on the remote.
fatal: The current branch x has no upstream branch.
The local branch isn’t linked to a remote branch yet, so a bare git push doesn’t know where to go.
Map another error
Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException