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. –
Kashmir git commit -m 'initial commit' should be double quoted. 'git commit -m "initial commit", at least on windows. –
Linger nothing added to commit but untracked files present Monas-MacBook-Pro:02_02 mona$ git push origin master error: src refspec master does not match any. error: failed to push some refs to 'https://github.com/monajalal/jupyter_notebooks.git' didn't work for me! –
Kelleykelli git push scheduler when my local branch was named sheduler. Once I fixed the local name to say scheduler it works. HAHA :) –
Urbannal git remote set-url origin <my_git_repo.git> and try to git add . , git commit -m "intial commit', git push origin master –
Myongmyopia git push -f heroku master:refs/heads/master and git push -f heroku HEAD:master - both don't work for the first time... –
Chapbook git status to check which files have you staged. –
Keewatin git branch -M <branch_name> –
Homelike master instead of main solve me problem –
Kaiak git push origin master to git push origin main –
Killigrew git init, and then tried to make the first commit. This was met with an error, and git told me to tell it who I am. After setting the user.email and user.name, I simply forgot to do the commit; and voila when I tried to push to a new, empty repo on GitHub, this very error occured. –
Stubbed 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. –
Doubleheader git push origin HEAD:master. But why something like git push --force origin master does not work? –
Convincing unfriendly error shows up. use git push origin <branch> instead of master in case you attempt to git checkout -b <branch> before any FIRST push after initial git remote add origin <url> –
Accrete git push --set-upstream origin refs/heads/the_remote_branch. Also you can create a script or alias that will do git push origin HEAD:/refs/heads/master with little typing. –
Humfrid git push origin HEAD:master --force, but I still can't do a normal git push . I'm curious what I need to do to get past this original error. –
Electroencephalogram --force-with-lease, which is safer that usual --force, especially when you use the repository not alone. –
Humfrid HEAD: prefix was exactly what i needed for this problem. i have local branches that look like dev/something-or-other and the remote is just dev. Apparently git was confused about the path-like branch names, so git push <remote> HEAD:dev worked perfectly. –
Garlaand git push -u origin HEAD:feature/random_name and that worked for me. –
Mob git show-ref helped to understand it. –
Skeie master is changed to main now. –
Backgammon git push -u origin main instead of git push -u origin master –
Guildhall git push origin HEAD:master solved my issue. Then if you want to use master branch then you can switch to master branch by git checkout master command. Thanks –
Gummy 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)
git commit -m 'reinitialized files'
git push origin master --force # <- caution, --force can delete others work.
git push origin BRANCH --force worked. Thank you! –
Prestissimo 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.
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" –
Severe -u option that was used here. –
Synonym git *create remote? –
Mikesell To fix it, re-initialize and follow the proper code sequence:
git init
git add .
git commit -m 'message'
git push -u origin master
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 –
Behring git branch -M main worked for me. –
Laspisa git branch -M main is important which is why it wasn't working for me. It expects master if you don't put anything. –
Sap 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. –
Synonym 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; –
Imperforate git push origin scheduler. HA! One letter off will kill you in programming. lol –
Urbannal dev branch from my local that does not exist yet on my local. I was in the main branch, so I had to do git checkout -b dev and then git push origin dev. Thank you. –
Tailwind main and master –
Reason I 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
I faced the same issue some days ago.
If you created a new repository nowadays (2020) then the default branch is main on GitHub.
You can check on GitHub now in your repository branches.
And you can also check the branch in the terminal by running the command:
git branch
So that's why you need to run
git push origin main
instead of
git push 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.
You probably forgot the command git add . after the git init command.
After the GitHub update 2000-10-01, you should use main instead of master.
Do it like this way...
.git file in your local directorygit initgit add .git commit -m"My first commit"master in your local projectgit remote add origin <remote repository URL past here from the GitHub repository>, and then type git remote -vgit push -f origin mastermain 2. mastermaingit checkout maingit merge mastergit pull origin maingit push -f origin mainNote: from 2020-10-01, GitHub decided use main instead of master branch to use as the default branch name.
Just add an initial commit. Follow these steps:
git add .
git commit -m "initial commit"
git push origin master
This worked for me.
If your branch is "main":
Run this command:
git push origin main
If your branch is "master":
Run this command:
git push origin master
I have faced the same issue, and this solved my problem:
Just make a branch:
git checkout -b "master"
After that,
git push -u origin master
Boom.
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.
Maybe the branch is main instead of master.
Try
git push origin HEAD:main
or
git push origin main
GitHub changed the default branch name from master to main.
So if you created the repository recently, try pushing the main branch:
git push origin main
This happens when you have added your file, forgot to commit and pushing. So commit the files and then push.
git add .git commit -m "message"git push origin branchPlease check for spelling mistakes because that could also give that error.
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
It happens if you forget to commit before pushing for the first time. Just run:
git commit -m "first commit"
To check the current status, git status.
And follow these steps as well:
git init
git add .
git commit -m "message"
git remote add origin "github.com/your_repo.git"
git push -u origin master
This just mean you forgot to do the initial commit, try
git add .
git commit -m 'initial commit'
git push origin master
I had the same problem when I missed to run:
git add .
(You must have at least one file, or you will get the error again.)
I also followed GitHub's directions as follows below, but I still faced this same error as mentioned by the OP:
git init
git add .
git commit -m "message"
git remote add origin "github.com/your_repo.git"
git push -u origin master
For me, and I hope this helps some, I was pushing a large file (1.58 GB on disk) on my MacOS. While copy pasting the suggested line of codes above, I was not waiting for my processor to actually finish the add . process. So When I typed git commit -m "message" it basically did not reference any files and has not completed whatever it needs to do to successfully commit my code to GitHub.
The proof of this is when I typed git status usually I get green fonts for the files added. But everything was red. As if it was not added at all.
So I redid the steps. I typed git add . and waited for the files to finish being added. Then I followed through the next steps.
I was facing the same issue and tried most of the answers here, But the issue was because of recent changes of GitHub renaming.
GitHub is gradually renaming the default branch of repositories from master to main.
https://github.com/github/renaming
Your new command would be:
git push origin main
instead of this:
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 2021, GitHub changed the default branch name to main. Previously it was master.
I suffered because I tried to push to master which did not exist and the branch at remote was main instead. Make sure you are using the correct branch name.
The command below worked for me
git push origin main
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
This will also happen if you have a typo in the branch name you're trying to push.
git add .
is all you need. 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"
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.
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
Double check that you're pushing the correct branch name. I encountered the same error and after looking at git show-ref I was able to see I was typing it in wrong, therefore, no ref.
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
This error occurs as you are trying to push an empty repository into the Git server. This can be mitigated by initializing a README.md file:
cat > README.md
Then type something, followed by Enter, and a Ctrl + D to save.
Then the usual committing steps:
git add .
git commit -m "Initial commit"
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
Try this:
git add .
git commit -m "your commit message"
git remote add origin *remote repository URL*
git push origin *your-branch-name*
Only commit solved this error:
git commit -m "first commit"
I also faced the same issue. In my case by mistake I made a commit before adding. After performing the steps in sequential order, I got it.
Also please make sure to give the correct branch name.
git init
git add .
git commit -m <Your commit message>
git remote add origin "your repository link here"
git push -u origin master
I got the same issue when I was doing my first push to a repository. I forgot to commit any changes and was trying to do
git push -u origin main
This was resolved by adding a commit and then execute:
git push -u origin main
This worked for me, resetting to remote master the repository:
git checkout master
git commit -a -m "your comment"
git push origin master
I was getting this error because my local branchname did not match the new remote branch I was trying to create with git push origin <<branchname>>.
I got this problem while adding an empty directory. Git doesn't allow to push an empty directory. Here is a simple solution.
Create the file .gitkeep inside of directory you want to push to remote and commit the "empty" directory from the command line:
touch your-directory/.gitkeep
git add your-directory/.gitkeep
git commit -m "Add empty directory"
In my case I cloned a repository, but I didn't switch to the branch locally.
I solved it by doing this:
Before making changes in code you should do this:
git checkout branch-name
Then make changes to your code
After that push the code to the branch:
git push -u origin branch-name
Also, if you are pushing your local repository first time to GitHub, you need to first create a main branch:
git branch -M main
And, then, after adding the origin (or whatever name you give to your remote) push the branch:
git push -u origin main
I did face the same problem, but in my case the following the exact steps from the beginning as given on the page when you create a new repository worked.
Just pasting that over here:
echo "# YYYY" >> README.md
git init
git add README.md
git commit -m "first commit"
git remote add origin https://github.com/XXXX/YYYY.git
git push -u origin master
Type the above in Git Bash. XXXX being the username and YYYY the repository name.
What worked for me was simply checkout to the branch that I want my code to push and then simply push your code.
git checkout -b branchname-on-which-i-will-push-my-code
git add .
git commit -m "my commit message"
git push origin branchname-on-which-i-will-push-my-code
Make sure you are pushing to the right branch or is there any typo. Check out your current working branch name with this command:
git show-branch
I had faced the same issue before. The issue was with my local branch name. It was different from the one I tried to push. Correcting branch name to the target one, I was able to push the changes.
Remember the local branch and target branch should be same.
I had a similar error. But Git tells me:
*** Please tell me who you are.
Run
git config --global user.email "[email protected]"
git config --global user.name "Your Name"
Or to set your account's default identity.
Omit --global to set the identity only in this repository.
Then the error goes away.
Another possible cause of this problem is if you misspell the branch name. So if you did what I did then the problem would be fixed by correcting:
git push origin mater
to
git push origin master
Check your commit title, because if you forget the git commit -m "xxxx" command, you get the same problem
git commit -m "initial commit"
I ran into the same snag. The solution was to push the code to the repository as though it were an existing project and not a brand new one being initialised.
git remote add origin https://github.com/Name/reponame.git
git branch -M main
git push -u origin main
In 2020:
If none of the 30+ answers has worked, you probably need to run git push origin main (master has been renamed to main at the time of writing this answer).
As one of the options for solving your problem:
git push origin HEAD
I think it's because you pushed an invalid branch.
Generally, because the repository does not have a common master branch (maybe development branch). You can use
git branch
to see branches.
This happened to me when I did not refer to the master branch of the origin. So, you can try the following:
git pull origin master
This creates a reference to the master branch of the origin in the local repository. Then you can push the local repository to the origin.
git push -u origin master
Maybe GitHub doesn't know who you are.
First you have to run:
git config --global user.email "[email protected]"
git config --global user.name "Your Name"
Try git show-ref
You might see refs/heads/live
This means you should do
git push -u origin live
I forgot to commit and then ran into this. Just commit.
I had the same issue just today. I created a new repo and cloned it to my machine. I committed my code and tried to push it. I got the same error. I observed that it is because I was using:
git push origin master
What I was doing wrong here is that I assumed my default branch to be master whereas the new default on GitHub is main. I pushed using:
git push origin main
and it worked fine.
My solution applies only to the newer repos or people facing this issue very recently because GitHub is replacing the main over master terminology. So if you get this error, make sure to check the branch you are pushing to and the branch name on GitHub.
men. If you want a branch named men you can use git checkout -b men and then you would be able to push this branch to remote. –
Fingerling For Repositories WIKI, I encountered this error also.
git show-branch
if shows master then
git push -u origin master
I had a similar issue. In my .gitignore file there was an asterisk, '*', defined. All the files were being ignored and therefore it failed.
I removed '*' and used all the standard Git commands that worked for me.
git add .
git commit -m "Initial commit"
git push -u origin main
I had already created a commit. Make sure you are pushing to the right branch.
I was typing git push origin master, but when I typed git branch I was on a v1 branch, so I had to type git push origin v1.
git push origin HEAD, or git push origin @ if you're using a recent version of Git, or git push origin head if you're using Windows or OS X. –
Filberte I had the same issue and fixed it using the following steps:
I created the files in the wrong directory, tried to do git push -u origin master, and I got the error.
Once I cd to the current directory, do git push -u origin master, and all is fine.
The problem I had was when trying to reset my repository. I wanted to delete all history and commit nothing. However, you have to add at least SOMETHING to commit, so I just created an empty text file, git add . and then git commit -m "Reset repository".
I had this problem once because i had a branch on my remote repo but not locally. I did:
git fetch && git checkout 'add remote branch name here' and it solved my problem.
Sometimes the problem occurs when you don't stage your changes, so to do this you need to run the following git command:
git add your_file_name.extension or git add . to add all changes.
At this point you need to commit your changes with:
git commit -m 'your commit message here'.
Once you have done all that, you just need to push your changes to remote repo with:
git push origin your_branch_name.
First you need to git init to create your own .git file, otherwise if you clone someones git folder it will not recognize your git credential. After you started git, then continue with git add. and git commit ...
You may run into this issue for multiple reasons.
1. Pending commit for the staged files
If you've added the changes by running git add command (i.e., git add .), and never committed those files then after and tried to push the branch into the remote repository. In this case, you'll face the error src refspec master does not match any.
2. Invalid local branch name
If you did a typo in the name of the branch, (i.e., mster instead of master), then it will lead you to this error. It means the branch you're trying to push into is not in the local repository.
First of all, make sure that you are using the master branch. In my case, the branch was main instead of master. I did:
git push origin main
You can see the result in this photo:
One reason for this month is probably be: GitHub has renamed the default "master" branch to "main" branch.
So, use git push origin main instead.
Update to previous answers.
Also, don't forget that GitHub has changed 'Master' to 'Main', so make sure you're pushing via:
git push origin main
For GitLab users, the updated version of GitLab will now have a 'main' branch as the default.
So you can try the following:
git push origin main
Reference: GitLab new Git default branch name is main
I encountered this issue and the root cause was I followed the steps as is mentioned in GitLab upon creating a new project:
without adding any file in the local directory before the push. Therefore it wasn't considered as commit, because there was nothing to commit (though you run git add . and git commit -m "initial commit" commands. Make sure you add some files in your local directory and only then will Git consider it as commit and then pushing resolved the error.
Regarding Aryo's answer: In my case I had to use the full URL of my local Git repository to push the file. First I removed all the files in the current directory and created README added it.
Added some more. Then I committed those files and at last pushed them, giving a proper URL to the repository. Here yourrepository is the name of the repository on the server.
rm -rf *
touch README
git add README
touch file1 file2
git add file1 file2
git commit -m "reinitialized files"
git push git@localhost:yourrepository.git master --force
git remote add origin <url>? –
Filberte If you want to create a new branch remotely in the origin, you need to create the same branch locally first:
$ git clone -b new-branch
$ git push origin new-branch
I was contributing to one GitHub repository, so I forked the project, cloned it, created my own branch, did some commits, and tried to push.
At this point I discovered that I cloned not my fork, but the original project repository (which I don't have permission to push to).
So I changed the .git/config to point origin to my repository.
At this point, when I tried to push, I was getting the error error: src refspec my_awesome_branch does not match any.
All I had to do was to touch any file and commit it (similar like you see it in this answer):
git touch README
git commit -m "fixing error in my git repo"
And then:
git checkout master
git pull origin master
git push origin master # This will tell my remote repository about my new branch
git checkout my_awesome_branch
git push origin my_awesome_branch # Now it will work
I faced this exact problem while dealing with VCS in Android Studio. It turns out all I had to do was:
Eureka! :D
For users of Bash within Cmder on Windows, make sure to create a new .ssh folder in your new home directory.
Go to your home directory cd ~.
Generate ssh keys ssh-keygen.
Leave all inputs blank (keep pressing enter)
Copy the id_rsa.pub file into your Github > Settings > SSH Keys
I got this error,
error: src refspec master does not match any.
when I tried to push a commit to GitHub, having changes (at GitHub).
git push -u origin branch-name - helped me to get my local files up to date
This works for me:
Just checkout the master branch:
git checkout -b master
git add .
git push origin master
Or use --force for forcing a change.
git push origin master --force
I had the same problem and discovered also that I had not committed any file, so when I tried to commit again, I got this error message:
*** Please tell me who you are.
Run
git config --global user.email "[email protected]"
git config --global user.name "Your Name"
to set your account's default identity.
Omit --global to set the identity only in this repository.
fatal: unable to auto-detect email address (got 'USER@WINDOWS-HE6I2CL.(none)')
Then all I did was add my email and name globally and then committed again:
git commit -m 'Initial commit'
Then pushed
git push -u origin master
If you have Visual Studio Code:
git stash)git initgit commit -m "first commit"git remote add origin https://github.com/YOURusername/YOURrepo.gitIf you have permissions to the repository, you can see:
> git push -u origin master
Fatal: AggregateException encountered.
To https://github.com/your_account/yourrepo.git
* [new branch] master -> master
> git status -z -u
> git symbolic-ref --short HEAD
> git rev-parse master
> git rev-parse --symbolic-full-name master@{u}
> git rev-list --left-right master...refs/remotes/origin/master
> git for-each-ref --format %(refname) %(objectname) --sort -committerdate
> git remote --verbose
> git show :ionic.config.json
> git check-ignore -z --stdin
I faced a similar error. The error was due to this command:
git push -u origin master
Subsequent commands worked for me.
Start with these commands
git init
git add .
git commit -m "second commit"
So before pushing it, run these commands to see what remote repository on GitHub our local repository is connected to and which branch are you on.
git remote
git branch
remote -->origin
branch --> main
git push -u remote branch
Or more specifically:
git push -u origin main
As of 1st October 2020, GitHub is changing the name of the master branch to main. This is what is causing the issue.
When someone types git push origin master they see this error
error: src refspec master does not match any error: failed to push some refs to 'https://github.com/username/reponame.git'
This can be fixed by using git push origin main. Hope this helps. I took quite some time to figure out why I couldn't push my commits to the master branch.
The issue is that you have not configured Git to always create new branches on the remote from local ones.
The permanent fix if you always want to just create that new branch on the remote to mirror and track your local branch is:
git config --global push.default current
Now you can Git push without any more errors!
A git clone of an empty GitHub repository will create a local repository with 'main' as a default branch, even if init.defaultBranch is set on master!
The Git transfert protocol v2, supported by GitHub, will communicate to the client the name of the remote default branch (now main for GitHub) to the local Git repository created by git clone.
That means adding and committing new commits will be done on 'main' branch, even if the Git client still consider master as the default branch.
No more "src refspec master does not match any." on your next push.
Initially, every file is in an untracked state. We need to add untracked files from the working directory to the staging area, and only then will Git start tracking the files. From the working directory, we move files to the staging area which are ready for the next commit, so that Git is prepared to take a snapshot of them to create a new version. You skipped the staging area and added only one file to the staging area.
First go to your local folder which you want to push and then follow these steps.
git init
git add .
git commit -m "First commit"
I recently came across this problem. I checked show-ref using git show-ref and checked whether
refs/heads/master
was present.
It was present, but still it was not working for me.
As I was writing
git push origin main
Later I changed this command with
git push origin master
and it worked perfectly fine for me.
push is always done on that branch which is selected. –
Valet I was on the wrong branch. Check your branch. I was on a 'master' branch instead of 'main'.
My problem was that I did not switch to the main branch before making a commit
git branch -M main
I too faced the same problem. But I noticed that my directory was empty when this error occurred. When I created a sample file and pushed again it worked. So please make sure before pushing that your folder is not empty!!
git branch
Rename the branch with the -mv flag:
git branch -mv origin master
After this, git branch should show master.
git branch ought to be explained. Please respond by editing (changing) your answer, not here in comments (but *** *** *** *** *** without *** *** *** *** *** "Edit:", "Update:", or similar - the answer should appear as if it was written today). –
Larkin Check that the current branch is master only. I faced the same issue and my branch was main. So running the following command did the work for me:
git push origin main
There are mainly two possibilities for this question. Let us consider this one by one.
It can be possibly be the error that, master branch does not even exist. In my case, it was named main, and not master. In this case, you need to replace master with main.
You haven't even committed your changes. If this is the case, then go for -->
git add .
git commit -m "initial commit"
git push origin <branch>
Then it should work.
Try it, and it will be good. :)
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
Use above commands you might be missing "git branch -M main" (this particular command)
This was an error I got when I started to learn Git. The cause of this error is when you add a remote origin to a Git repository, Git on the system puts it on the master branch, but GitHub has moved from master to main here.
To solve this issue:
Use git checkout -b main to switch to the main branch.
Use git pull origin main to pull the main branch, and add proper flags if you want to merge or rebase the branches.
Now you can use git push origin main to push your work to the main branch.
A few months later...
I just found another cool way of doing this:
git config --global init.defaultBranch main
Using this, you can get rid of the error for all later times. To test it out, enter the above command and initialize an empty Git repository locally, make a random file in it, and do git add . and git commit -m "message".
To check the branch name, do git branch. It should now show main.
None of the above solutions worked for me when I got the src-refspec error.
My workflow:
I fixed the error by simply making a new branch, and pushing again.
(The weird thing was, I couldn't simply just rename the branch - it gave me fatal: Branch rename failed.)
I also received this problem, but it was because I accidentally shut down my server before doing the push. This too will cause the same error.
Error from Git:
error: src refspec master does not match any.
Fixed with this step:
git commit -m "first commit"
Before I ran:
git add <files>
And after I ran:
git push -u origin master
In my case the issue, occuring on Windows, seemed to have something to do with us adding a prefix like feature\ to branch names. We were trying to create and push a branch with such a prefix (say, feature\branch) but there was already a different branch, with a different name prefixed with Feature\ (say, Feature\otherbranch). This means that on Windows the new branch was placed in the same refs\heads\Feature folder. Git may be case-sensitive but Windows filesystem isn't. It helped once we checked out the local branch named Feature\branch.
I had this error, and it was a problem with the name of the branch because I used the character "&". I just skipped it by "^&" and it worked.
If it doesn't recognize that you have a master branch, just create it and commit again.
To create a master branch:
git checkout -b master
If you are using Git Bash on Windows, try restarting it. It worked for me!
Permissions issue? Resolution: fork it
I got this error because I didn't have any push permission to the repository, so I had to fork it. And then I did execute pull, commit, and push commands once again on the forked repository.
This could also happen if you have a typo in the name of your branch and therefore you're trying to push something that doesn't really exists! ha!
In my case, I actually created the branch with an incorrect name (by accident, obviously) and it was called fetaure/<something> and was trying to push feature/<something>
The brain will read the word just as a unit and therefore sometimes both words look the same but they're not! ha!
Just be sure you don't have a typo in the name of the branch! (or better said, check that the branch you want to push actually matches the branch you have defined locally, specially if you are manually doing the first push of a newly created branch git push origin feature/<newBranch>)
I made my first major commit today. I tried a lot of the guide given, but it kept spitting errors.
git initgit commitTo send to your GitHub repository, first ensure that your username and email has been added:
git config --global user.name 'Your name'
git config --global user.email '[email protected]'
Continue:
git remote add origin https://github repo url
To push to the repository:
git push -u origin 'https://github.repo url'
It loads the commits to your repository.
Done!!!
Make sure you do not have an invisible typo in a branch name:
git branch
Output:
master
* <U+0096>your_branch_name
There is an invisible <U+0096> character which probably got there by pasting the branch name.
Rename your current branch to the correct value and then try push again:
git branch -m your_branch_name
Also check if you have changed the branch name
For me, I had changed the branch name from add-status-conditions to add-status-condition and failed to notice the missing s at the end. Renamed the branch correctly and did git push origin add-status-conditions -f.
That worked for me.
git init
First command first... First, we need to initialize // and this should work for sure!
git init
git add .
git commit -m "message"
prompt me to enter email and user name
git config --global user.email "[email protected]"
git config --global user.name "Your Name"
After entering the above details, the files are commit and pushed successfully:
git push
In my case, the error occurred when I was pushing changes to the branch which I only had locally. The remote branch did not exist with the same name. I resolved the error with the following command:
git push --set-upstream origin "your-branch-name"
I think the problem stems from adding and committing your node_modules folder.
When you use git add ., you may get that infinite scroll as if it is adding several files. If so, you are not only adding your scripts but also the node_modules folder which is large in size.
The best solution is to create a .gitignore file, inside of which you paste that # dependencies /node_modules.
Now when you add your files, Git will ignore the node_modules folder.
Updated answer: Make sure all changes are committed.
Then type : git push Before this make sure to make a personal access token, GitHub uses this now. Then type out your GitHub username (after typing git push) then paste your personal access token in the password input.
After all this you should be able to see your changes in GitHub!
I was facing this issue because I had made a branch and I had to use that branch and after that it was resolved by using this.
git push origin branch_name
For me, it seemed to be because I had already done the commit process, so I got this after trying to commit again.
Your branch is ahead of 'origin/main' by 1 commit.
(use "git push" to publish your local commits)
Since I saw that the path was origin/main, I pushed to main instead of master and it worked.
NB: Check to ascertain if the primary branch is main or master.
As of 2022.
sudo git push -v --progress "origin" : origin/prod_18aug2022
This worked for me when pushing from a local to remote branch.
My branch was named bugfix-22112022/5v8ST5Q6/181-kontaktformular-eingabe-nach-anmeldung-übernehmen, <-- yes it had a comma in it and I thought the comma is not part of it and deleted it when trying to push...
I renamed my branch:
git branch -m bugfix-22112022/5v8ST5Q6/181-kontaktformular-eingabe-nach-anmeldung-übernehmen
This issue can be solved by reinitializing Git in the project folder:
# Type the following on the CMD
git init
# Then try pushing your code online
git push
You may encounter this problem when any of your folders is already linked to another Git repository.
Visit the folder that is not being added and delete the .git file (if you do not want it to link to that repository any more) from there and try adding and committing again.
I fixed this issue with using this command before commit and it worked:
git add .
Change master to main. That should work.
git push origin main
git push origin master but should have been using git push origin main –
Manslaughter Sometimes these type of error exits when your GitHub personal-access-token as expired. As of in my case the same error occurred, but go on executing all the solutions none of them worked, instead it showed that my personal-access-token as expired. To know more about personal-access-token do refer these link- https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens
I just got this error while trying to push stuff into a new repository on GitHub. I had created the Git repository locally, plus I had created the repository on GitHub using the Web GUI (including a LICENSE file).
The problem went away after I pulled the LICENSE file from the otherwise empty GitHub repository into my local repository. After that, I could push with no problems.
I had an extremely long local branch name.
git branch -m new_shorter_branch_name
fixed the problem.
In my case fastlane match nuke development (which deletes the development certificates and profiles from the git credential store and the Developer Portal) tried to push master but we don't have master. Since we have two different teams we have also 2 different branches. What solved the problem was to call tell match about the correct branch:
fastlane match --git_branch <your_branch> nuke development
fastlane match nuke development deletes the development certificates and profiles from the git credential store and the Developer Portal (I edited my answer). –
Macintosh The thing that worked for me was
git commit -m "initial commit"
after running the command.
Instead of running the "git push -u origin master", use:
git push -u origin main
If you had the problem where it worked with "master" or with "main", but you want to change the name of the branch:
You can go to the repository settings and change it here:
I post this answer, because it really confused me and I had to dig some details.
"git init" resulted in the master branch being created as the top branch. GitHub's default top branch has been renamed from "master" to "main", due to a hilarious discussion about words... More is here, incl. the solution.
TLDR:
To solve the problem, I had to rename my local top branch from "master" to "main"... — git branch -m master main
These sort of things hold people back from serious coding work, but I guess ultimately words do matter ;)
git init is giving you master as the default unborn branch, you need to update your Git, because modern Git uses main just like GitHub. — Final comment, read my biteinteractive.com/of-git-and-github-master-and-main which tells you more about this problem than you ever ever ever wanted to know. –
Conlin I had the same error; this is how mine was solved:
git config --global user.email "YOUR EMAIL"
git config --global user.name "YOUR NAME"
© 2022 - 2024 — McMap. All rights reserved.
git statusto get the proper one. – Groffgit commitcan cause this error, as well! – Besprinklegit addwith dot or some files this error also will appear. – Recruitmentgit branch -M mainand it will work – Masbategit pull origin main, after that I could push my changes. I believe this overwrites your branch though – Determinate