I clone my repository with:
git clone ssh://xxxxx/xx.git But after I change some files and add and commit them, I want to push them to the server:
git add xxx.php git commit -m "TEST" git push origin master But the error I get back is:
error: src refspec master does not match any. error: failed to push some refs to 'ssh://xxxxx.com/project.git' Maybe you just need to commit. I ran into this when I did:
mkdir repo && cd repo git init git remote add origin /path/to/origin.git git add . Oops! Never committed!
git push -u origin master error: src refspec master does not match any. All I had to do was:
git commit -m "initial commit" git push origin main Success!
git add --all in case you wish to add all the files Or you can selectively add files. Then git commit -m "Initial comment", git push origin master. This will surely work.
git commit -m 'initial commit' should be double quoted. 'git commit -m "initial commit", at least on windows.
git show-ref to see what refs you have. Is there a refs/heads/master?Due to the recent "Replacing master with main in GitHub" action, you may notice that there is a
refs/heads/main. As a result, the following command may change fromgit push origin HEAD:mastertogit push origin HEAD:main
git push origin HEAD:master as a more local-reference-independent solution. This explicitly states that you want to push the local ref HEAD to the remote ref master (see the git-push refspec documentation).
git show-ref showed my branch; the git push origin HEAD:<branch> worked for me.
git push origin HEAD:master. But why something like git push --force origin master does not work?
master is changed to main now.I also had a similar error after deleting all files on my local computer, and I have to clean up all files in the repository.
My error message was something like this:
error: src refspec master does not match any. error: failed to push some refs to 'git@github ... .git' And it was solved by executing the following commands:
touch README git add README git add (all other files) or you can also use # git add --all :/ git commit -m 'reinitialized files' git push origin master --force # <- caution, --force can delete others work. 
git push origin BRANCH --force worked. Thank you!
git push -u origin master error: src refspec master does not match any. For that you need to enter the commit message as follows and then push the code:
git commit -m "initial commit" git push origin master Successfully pushed to master.
For me I had to make sure the public key is properly configured on the server (appended in ~/.ssh/authorized_keys) and in GitHub/Bitbucket (added to my SSH keys on GitHub or Bitbucket) - they need to match. Then:
git add --all :/ git commit -am 'message' git push -u origin master 
This happened to me in a brand new repository after I ran git add with only an empty directory.
As soon as I added a file (e.g. a git add README.md), then git push worked great.
Missing or skipping git add . or git commit may cause this error:
git push -u origin master Username for 'https://github.com': yourusername Password for 'https://[email protected]': error: src refspec master does not match any. error: failed to push some refs to 'https://github.com/yourusername/foobar.git' To fix it, reinitialize and follow the proper sequence:
git init git add . git commit -m 'message' git *create remote git push -u origin master 
git remote add __REMOTE_NAME__ __URL_OR_SSH__, and above the remote name is "origin"-u option that was used here.
git *create remote?I had the same problem when I was creating a new repository on GitHub and linking it with my React app in the client computer I have.
I used the following steps:
git init git commit -m "first commit" git branch -M main git remote add origin "_git repository link here_" git push -u origin main But as you can see, my mistake was not using the git add . command. I did this mistake, because I already had the README.md file and GitHub instructs us with basic commands while creating the repository.
My solution is to use git add . after the git init command.
Use the following set of commands in the same order to overcome the problem:
git init git add . git commit -m "first commit" git branch -M main git remote add origin "_git repository link here_" git push -u origin main 
git add . then git commit -m "first commit", then push again
git branch -M main worked for me.
git branch -M main is important which is why it wasn't working for me. It expects master if you don't put anything.To fix it, re-initialize and follow the proper code sequence:
git init git add . git commit -m 'message' git push -u origin master This happens too when you are in a specific branch and try to push another branch that does not exist yet, like:
$ git branch * version-x # you are in this branch version-y $ git push -u origin master error: src refspec master does not match any. error: failed to push some refs to 'origin_address' 
-u may have helped here.
master, so you can't push it. You either want to push an existing branch – or create the master branch and then push it, like this: git checkout -b master; git push -u origin master;
git push origin scheduler. HA! One letter off will kill you in programming. lolI faced the same problem, and I used --allow-empty:
$ git commit -m "initial commit" --allow-empty ... $ git push ... One of main reasons of this problem is that some Git servers, such as BitBucket, don't have their master branch initialized when a fresh repository is cloned.
Make sure you've added first, and then commit/ push:
Like:
git init git add . git commit -m "message" git remote add origin "github.com/your_repo.git" git push -u origin master Two possibilities:
1- Either you forgot to include the .gitignore file.
Here are all the steps required:
Create an empty Git repository on remote,
On local, create the .gitignore file for your project. GitHub gives you a list of examples here
Launch a terminal, and in your project do the following commands:
git remote add origin YOUR/ORIGIN.git git add . git commit -m "initial commit or whatever message for first commit" git push -u origin master 2- Or you are trying to create a new GitHub project.
GitHub replaced master with main as the default branch name. To resolve the issue:
.git folder if it existsIn the terminal:
git init git add . git commit -m "YOUR FIRST MESSAGE HERE" git branch -M main git remote add origin _GIT_LINK_TO_PROJECT_HERE_ git push -u origin main 
For me,following worked to move untracked files:
git add --all Next, I followed similar steps
git commit -m "First commit" Then,
git remote add origin git@github..... Last but not the least:
git push -u origin master As you do this, Windows security will pop up asking for your username and password.
If your branch is called "main":
Run this command:
git push origin main If your branch is called "master" instead, run this command:
git push origin master 
My issue was that the 'master' branch hadn't been created locally yet.
A quick
git checkout -b "master" created the master branch, at which point, a quick
git push -u origin master pushed the work up to the Git repository.
If you get this error while working in detached HEAD mode, you can do this:
git push origin HEAD:remote-branch-name See also: Making a Git push from a detached head
If you are on a different local branch than the remote branch, you can do this:
git push origin local-branch-name:remote-branch-name This just mean you forgot to do the initial commit, try
git add . git commit -m 'initial commit' git push origin master Short answer: This error means the branch you want to push in remote doesn't exist!
In my case, starting from October 2020, the repositories created since then had the main branch instead of the previous master branch. So all I had to do was this:
git push -u origin main You may skip -u flag if the upstream is set (like in case you had cloned it already).
Bingo! That worked for me!
In the scenario where you check out the code from an external repository (GitHub), and want to import it in personal / internal system, this command really shines:
git push --all origin This pushes all local branches to the remote, without checking refs and without insisting on commits.
I had the same problem. I did it by the following steps:
1. git commit -m 'message' 2. git config --global user.email "your mail" 3. git config --global user.name "name" 4. git commit -m 'message' 5. git push -u origin master All you need is:
git add . That code tracks all untracked files in your directory.
You need to configure your Git installation if it is the first time that you use it, with:
git config --global user.email "[email protected]" git config --global user.name "Your Name" At the end of 2020, GitHub changed its master branch to main branch.
I noticed GitHub created a new branch master and this is not the main branch when I am using git push -u origin master:
Now when I try to use git push -u origin main, to push directly to main branch it gives me this error:
I faced this error:
src refspec main does not match any error: failed to push some refs to 'https://github.com/<my_project_name>.git I fixed it using these steps after my first commit to main.Change URL for your GitHub in the following code:
git branch -M main git remote add origin https://github.com/Sidrah-Madiha/<my_project_url>.git git push -u origin main 
In case if you are facing this problem even after doing git init and pushing your initial commit. You can then try the following,
git checkout -b "new branch name" git push origin "new branch name" Your code will be pushed as a new branch.
I had the same issue. Turns out that I was pushing to master branch, while the original branch was main. You can check it using git show-ref.
If it shows refs/head/master, just change your branch to main. Here is what you can do:
git add . git commit -m "message" git branch -M main git push -u origin main -f Consider:
git push -u origin master Output:
error: src refspec master does not match any.
error: failed to push some refs to 'http://REPO.git'
This is caused by the repository still being empty. There aren't any commits in the repository and thus there isn't any master branch to push to the server.
It worked for me
Resolution
git initgit commit -m "first commit"git add appgit commit -m "first commit"git push -u origin masterMay be your current branch has no upstream branch. Try these commands when you are going to push for the first time.
git init git add . git status git commit -m "initial commit" git remote add origin "github.com/your_repo.git" git push --set-upstream origin master I forgot to do a "git pull origin master" after commit and before push and it caused the same problem: "src refspec master does not match any when pushing commits in git".
So, you should do:
1. git add . 2. git pull origin master 3. git commit -am "Init commit" 4. git push origin master To avoid getting into this error in 2021 and onwards, use this command before using git init
git config --global init.defaultBranch main This tells your git to use main as the default branch name always, instead of master
git addwith dot or some files this error also will appear.