DevOps

Overview The error “fatal: HEAD is not a valid object” means Git cannot resolve the name HEAD to a commit. This happens when a repository has no commits yet, when HEAD points to a branch that does not exist, or when refs are......

Overview Git prints: fatal: ambiguous argument '<thing>': unknown revision or path not in the working tree. Meaning: Git couldn’t resolve the token you passed (e.g., feature, v1.2, src/app.js) as either a valid revision (commit,......

What these errors mean fatal: bad revision: Git can’t resolve the revision/range you asked for (branch, tag, commit, or range like A..B). unknown revision or path not in the working tree: Git can’t find the ref, or it thinks your argument......

What the error means You are on a local branch that doesn’t know which remote branch it should track. As a result, commands like git pull, git push, and git status can’t infer where to read from or write to, and Git prints: fatal: no......

Overview The error “fatal: The upstream branch of your current branch does not match” occurs when you run git push with Git’s default push mode (simple) and your local branch tracks a differently named remote branch. Example: you are on......

Overview You see this error when you push to a remote repository whose currently checked-out branch is the same branch you’re updating: fatal: refusing to update checked out branch Git blocks this because updating a checked-out branch......

Overview Git 2.27+ warns on git pull if you haven’t told it how to handle divergent histories: Merge (default historically): create a merge commit Rebase: replay your local commits on top of upstream Fast-forward only: refuse to merge;......

What this error means Git blocks a rebase when your working tree has local changes that would be lost or conflicted by applying upstream commits. The error typically looks like: error: Your local changes to the following files would be......

What this error means Git refuses to merge (e.g., during git pull) when you have local modifications to tracked files that would be overwritten by incoming changes. It’s a safety check so you don’t lose work. Common contexts: git pull......

What this error means Git stops you from switching branches when files in your working tree differ from HEAD and would be overwritten by the target branch. This prevents data loss. Typical message: error: Your local changes to the......

What this error means Git stops a merge (or pull) if it would write a path that currently exists as an untracked file in your working tree. Git refuses to proceed to avoid data loss. Typical triggers: You created local files that aren’t......

Overview This guide shows practical ways to fix Git rename conflicts you may see during merges or rebases: CONFLICT (rename/modify) CONFLICT (rename/rename) CONFLICT (rename/delete) or (delete/rename) Key idea: resolve both the final......