DevOps

What this error means Git uses libcurl to connect over HTTPS. The error “fatal: unable to access …: SSL certificate problem” means TLS verification failed because Git could not build a chain of trust from the server’s certificate to a......

Overview Git LFS replaces large files in Git with small pointer files and downloads real content during checkout via the smudge filter. When that download fails, you’ll see errors like: smudge filter lfs failed Error downloading object:......

What this error means GitHub rejects pushes that include any Git object larger than 100 MB. You may also see a warning at 50 MB. The error appears even if the large file was deleted in a later commit—if it exists anywhere in history, the......

Overview A detached HEAD means your working directory points to a commit, not a branch. Commits you make here are valid but unreferenced by any branch. To keep or move them, create a branch or cherry-pick onto the right branch. If you’ve......

Overview The error fatal: You are not currently on a branch occurs when HEAD points directly to a commit instead of a branch tip. This is a detached HEAD state. Actions that move a branch (pull, merge, revert) fail because there is no......

Overview Git blocks git branch -d <name> if the branch’s commits are not reachable from your current branch (often main or develop). This protects unmerged work from accidental loss. You can: Integrate the work (merge, rebase, or......

Overview This error happens when you try to delete a local branch that is currently checked out in your main working directory or in another linked worktree. Git prevents deletion to avoid corrupting a checked-out branch. Typical......

What this error means Git shows "fatal: A branch named '<name>' already exists" when you try to create a branch with a name that already exists in your local repository. This happens with commands like: git branch......

Overview This error appears when your current local branch has no tracking (upstream) branch configured, or the remote branch it used to track no longer exists. Common triggers: Running git pull on a new local branch that hasn’t been......

Overview The error 'CONFLICT (content): Merge conflict in <file>' appears when Git cannot automatically merge changes. It inserts conflict markers into the file, and the merge or rebase pauses until you resolve, stage, and......

What this error means Git refuses to operate on repositories it considers unsafe. This typically happens when the repository directory (or its .git directory) is owned by a different user than the process running Git, or when permissions......

What this error means Git 2.35+ added a safety check (in response to CVE-2022-24765) that blocks operations in repositories whose ownership does not match the current user. You’ll see: fatal: unsafe repository ('…' is owned by someone......