How to fix error: src refspec main does not match any in Git

GitBEGINNERLOWUpdated Dec 6, 2025· 400 views

This error occurs when you try to push to a branch that doesn't exist locally, typically because no commits have been made yet or the branch name doesn't match between local and remote repositories.

Quick fix

Fixes error: src refspec main does not match any

git log --oneline
  1. Check if you have any commits
  2. Stage and commit your files
  3. Verify your local branch name
  4. Rename your branch if needed
git — error
git log --oneline
error: src refspec main does not match any

What this error means

The "src refspec main does not match any" error is Git's way of telling you that the branch you're trying to push doesn't exist in your local repository. A "refspec" is Git's internal reference specification that maps local branches to remote branches. When you run a command like `git push origin main`, Git looks for a local branch called "main" to push. If that branch doesn't exist locally - either because you haven't created any commits yet, or because your local branch has a different name (like "master") - Git cannot find a matching reference and throws this error. This is one of the most common Git errors, especially for developers setting up new repositories or those transitioning between the old "master" default branch name and the newer "main" convention adopted by GitHub in 2020.

Typical symptoms

  • Running git push origin main fails with 'src refspec main does not match any'
  • The error occurs immediately after initializing a new repository
  • Push commands fail even though you've added files with git add
  • The error mentions a branch name that doesn't appear when you run git branch
  • CI/CD pipelines fail during the push step with this error

Common causes

  1. No commits have been made yet - the branch doesn't exist until you create at least one commit
  2. Branch name mismatch between local (master) and remote (main) due to different Git defaults
  3. Typo in the branch name used in the push command
  4. The local branch was deleted or never created
  5. Using git init locally while the remote repository expects a different default branch name

How to fix "error: src refspec main does not match any"

1Check if you have any commits

First, verify whether you have made any commits. A branch doesn't technically exist until it has at least one commit:

bash
git log --oneline

If this shows "fatal: your current branch 'main' does not have any commits yet" or similar, you need to create a commit first.

2Stage and commit your files

If you haven't committed yet, add your files and create an initial commit:

bash
git add .
git commit -m "Initial commit"

After committing, the branch will exist and you can push.

3Verify your local branch name

Check what branches exist locally and which one you're on:

bash
git branch

The current branch is marked with an asterisk (*). If you see "master" but are trying to push "main", that's the problem.

4Rename your branch if needed

If your local branch is named "master" but you want to push to "main", rename it:

bash
git branch -M main

The -M flag forces the rename even if the target branch name already exists locally.

5Push with the correct branch name

Now push using the correct branch name:

bash
git push -u origin main

The -u flag sets up tracking so future pushes can be done with just git push.

6Alternative: Push using HEAD reference

If you're unsure of your branch name, you can push the current HEAD to a specific remote branch:

bash
git push origin HEAD:main

This explicitly pushes your current commit to the remote "main" branch regardless of your local branch name.

Advanced notes

### Setting Default Branch Name Globally

To avoid this issue in future projects, configure Git to use "main" as the default branch name:

bash
git config --global init.defaultBranch main

### Understanding Refspecs

A refspec has the format <src>:<dst>. When you run git push origin main, Git interprets this as git push origin main:main - push local branch "main" to remote branch "main". The error occurs when the source (src) part doesn't match any local reference.

### Empty Repositories

When you create a new repository on GitHub/GitLab without initializing it (no README, .gitignore, or license), the remote repository is completely empty. Your first push creates the initial branch. Make sure you've committed locally before pushing.

### CI/CD Considerations

In CI/CD pipelines, this error often occurs when:
- The pipeline checks out a detached HEAD instead of a branch
- The branch name in the pipeline configuration doesn't match the actual branch
- The repository is shallow cloned without the branch reference

Use git push origin HEAD:refs/heads/main for more explicit control in CI environments.

Frequently asked questions

What does "error: src refspec main does not match any" mean?
The "src refspec main does not match any" error is Git's way of telling you that the branch you're trying to push doesn't exist in your local repository. A "refspec" is Git's internal reference specification that maps local branches to remote branches. When you run a command like git push origin main, Git looks for a local branch called "main" to push.
How do I fix "error: src refspec main does not match any"?
This error occurs when you try to push to a branch that doesn't exist locally, typically because no commits have been made yet or the branch name doesn't match between local and remote repositories.
What causes "error: src refspec main does not match any"?
No commits have been made yet - the branch doesn't exist until you create at least one commit Branch name mismatch between local (master) and remote (main) due to different Git defaults Typo in the branch name used in the push command
Is the "error: src refspec main does not match any" error serious?
It is a low-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading