How to fix fatal: Not a valid object name: 'HEAD' in Git

GitBEGINNERMEDIUMUpdated Dec 1, 2025· 224 views

This Git error occurs when HEAD cannot reference a valid commit, typically in a newly initialized repository with no commits, or when the HEAD reference has become corrupted. The fix usually involves making an initial commit or resetting HEAD to a valid branch.

Quick fix

Fixes fatal: Not a valid object name: 'HEAD'

# Check what HEAD points to
cat .git/HEAD

# Try to list commits (will fail if none exist)
git rev-parse HEAD
  1. Check if the repository has any commits
  2. Create an initial commit for empty repositories
  3. Reset HEAD to the correct branch
  4. Recover from a remote repository
git — error
# Check what HEAD points to
cat .git/HEAD
# Try to list commits (will fail if none exist)
git rev-parse HEAD
fatal: Not a valid object name: 'HEAD'

What this error means

When Git displays "fatal: Not a valid object name: 'HEAD'", it means the HEAD reference in your repository does not point to a valid commit object. HEAD is a special pointer that Git uses to track your current position in the repository's commit history. This error most commonly appears in two scenarios: either you have a brand new repository that has been initialized with `git init` but has no commits yet, or the HEAD reference has become corrupted or points to a non-existent branch. In an empty repository, HEAD typically points to "refs/heads/main" or "refs/heads/master", but since no commits exist, that branch reference doesn't actually exist yet. Understanding this distinction is important because the solution depends on the root cause. For new repositories, you simply need to create your first commit. For corrupted repositories, you may need to repair the HEAD reference or recover from a remote.

Typical symptoms

  • Git commands like `git branch`, `git log`, or `git diff` fail with "Not a valid object name" error
  • Running `git show HEAD` returns an error instead of displaying commit information
  • CI/CD pipelines fail during checkout or build steps with HEAD-related errors
  • Creating new branches with `git checkout -b` or `git branch` fails
  • The `.git/refs/heads/` directory is empty or missing the expected branch file

Common causes

  1. Repository was just initialized with `git init` but no commits have been made yet
  2. HEAD points to a branch that does not exist (e.g., refs/heads/main when only master exists)
  3. The .git/HEAD file is corrupted or contains an invalid reference
  4. Git version mismatch between local and remote systems causing reference incompatibility
  5. Nested repository created by running `git init` inside an existing repository
  6. The .git/objects directory is corrupted or missing commit objects

How to fix "fatal: Not a valid object name: 'HEAD'"

1Check if the repository has any commits

First, verify whether your repository has any commits by checking if the HEAD reference points to an existing branch:

bash
# Check what HEAD points to
cat .git/HEAD

# Try to list commits (will fail if none exist)
git rev-parse HEAD

If you see "fatal: ambiguous argument 'HEAD'" or similar, the repository likely has no commits.

2Create an initial commit for empty repositories

If the repository is empty, create your first commit to establish a valid HEAD:

bash
# Create a file and make the first commit
echo "# Project" > README.md
git add README.md
git commit -m "Initial commit"

Alternatively, create an empty commit without any files:

bash
git commit --allow-empty -m "Initial commit"

After this, HEAD will point to a valid commit and the error should be resolved.

3Reset HEAD to the correct branch

If HEAD points to the wrong branch (e.g., "main" when your branch is "master"), fix it with:

bash
# Check available branches
ls .git/refs/heads/

# Point HEAD to an existing branch
git symbolic-ref HEAD refs/heads/master
# Or for main branch:
git symbolic-ref HEAD refs/heads/main

This command updates the symbolic reference without modifying any files.

4Recover from a remote repository

If you have a remote with valid commits, fetch and reset to recover:

bash
# Fetch all branches from remote
git fetch --all --prune

# Create local branch tracking the remote
git checkout -B main origin/main
# Or:
git checkout -B master origin/master

This downloads the commit history and establishes a valid local branch.

5Clone a fresh copy as last resort

If the repository is severely corrupted and you have a remote backup, the safest option is to clone fresh:

bash
# Backup any local changes first
cp -r my-repo my-repo-backup

# Clone a fresh copy
git clone <remote-url> my-repo-fresh

# Copy over any uncommitted work from backup

This ensures you get a clean repository state from the remote.

Advanced notes

### Understanding HEAD in Git

HEAD is stored in .git/HEAD and typically contains a symbolic reference like ref: refs/heads/main. When you check out a specific commit (detached HEAD state), it contains the commit SHA directly.

### CI/CD Pipeline Considerations

In CI environments like Jenkins or GitHub Actions, this error often occurs because:
- Shallow clones (--depth 1) may not include the referenced commit
- The checkout happens before HEAD is properly set
- Workspaces aren't fully cleaned between runs

Solutions for CI:

yaml
# GitHub Actions - ensure full history
- uses: actions/checkout@v4
  with:
    fetch-depth: 0

### Bare Repositories

Bare repositories (created with git init --bare) will show this error until they receive their first push. This is normal and expected.

### Git Version Compatibility

If you see this error when interacting with remote repositories, ensure Git versions are compatible between your local machine and remote server. Significant version differences (e.g., 1.x vs 2.x) can cause reference handling issues.

Frequently asked questions

What does "fatal: Not a valid object name: 'HEAD'" mean?
When Git displays "fatal: Not a valid object name: 'HEAD'", it means the HEAD reference in your repository does not point to a valid commit object. HEAD is a special pointer that Git uses to track your current position in the repository's commit history. This error most commonly appears in two scenarios: either you have a brand new repository that has been initialized with git init but has no commits yet, or the HEAD reference has become corrupted or points to a non-existent branch.
How do I fix "fatal: Not a valid object name: 'HEAD'"?
This Git error occurs when HEAD cannot reference a valid commit, typically in a newly initialized repository with no commits, or when the HEAD reference has become corrupted. The fix usually involves making an initial commit or resetting HEAD to a valid branch.
What causes "fatal: Not a valid object name: 'HEAD'"?
Repository was just initialized with git init but no commits have been made yet HEAD points to a branch that does not exist (e.g., refs/heads/main when only master exists) The .git/HEAD file is corrupted or contains an invalid reference
Is the "fatal: Not a valid object name: 'HEAD'" error serious?
It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading