Message 'src refspec master does not match any' when pushing commits in Git

Question

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'

Answer 1

Maybe you just need to commit. I ran into this when I did:

mkdir repo && cd repo
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!

Answer 2

1. Try 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 from git push origin HEAD:master to git push origin HEAD:main

2. You can try 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).

Answer 3

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.

Answer 4

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.

Answer 5

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

Answer 6

I found this happened in a brand new repository after I Git added only a directory.

As soon as I added a file (e.g. a README), Git push worked great.

Answer 7

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://yourusername@github.com': 
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

Answer 8

To fix it, re-initialize and follow the proper code sequence:

git init
git add .
git commit -m 'message'
git push -u origin master

Answer 9

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'

Answer 10

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

Answer 11

I faced the same problem, and I used --allow-empty:

$ git commit -m "initial commit" --allow-empty
...
$ git push
...

Supplement

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.

Answer 12

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 branch on 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

Goodluck

Answer 13

Problem faced

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:

Commands used before the problem

git init
git commit -m "first commit"
git branch -M main
git remote add origin "_git repository link here_"
git push -u origin main

My mistake

But as you can see my mistake was not using the git add . command I did this mistake because I already had README.md file and GitHub instructs us with basic commands while creating the repository.

My solution

My solution is to use git add . after 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

Answer 14

Two possibilities :

1- Either you forgot to include the .gitignore file.

Here are all the steps required:

1. Create an empty Git repository on remote,

2. On local create the .gitignore file for your project. GitHub gives you a list of examples here

3. 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 :

1. On your local project:
   1. remove the .git folder if it exists
   2. recreate a clean repository by launching the following in your project:

in 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

Answer 15

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.

Answer 16

You probably forgot the command git add . after the git init command.

Answer 17

After the GitHub update 01.10.20 you should use main instead of master.

Do it like these way...

1. Create a repository on GitHub
2. Delete existing .git file on your local directory
3. Go to local project directory and type git init
4. git add .
5. git commit -m"My First Commmit"
6. Now check your branch name it will be master in your local project
7. git remote add origin <remote repository URL past here from the github repository> then type git remote -v
8. git push -f origin master
9. Now check the github repository you will see two branch 1. main 2. master
10. In your local repository create new branch and the branch name will be main
11. git checkout main
12. git merge master
13. git pull origin main
14. git push -f origin main

Note: from 01.10.20 github decided use main instead of master branch use default branch name

Answer 18

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.

Answer 19

Just add an initial commit. Follow these steps:

• git add .

• git commit -m "initial commit"

• git push origin master

This worked for me.

Answer 20

Feb, 2022 Update:

If your branch is "main":

Run this command:

git push origin main

If your branch is "master":

Run this command:

git push origin master

Answer 21

Maybe the branch is main instead of master

try

git push origin HEAD:main or git push origin main

Answer 22

I have faced the same issue,

solved my problem.

just make a branch:

git checkout -b "master"

after that

git push -u origin master

bomm.

hope it will be solved.

Answer 23

This just mean you forgot to do the initial commit, try

git add .
git commit -m 'initial commit'
git push origin master

Answer 24

1. First, git add .
2. Second, git commit -m "message"
3. Third, git push origin branch

Please check for spelling mistakes because that could also give that error.

Answer 25

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.

Answer 26

It happens if you forget to commit before pushing for the first time. Just run:

git commit -m "first commit"

Answer 27

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

Answer 28

This happens when you have added your file, forgot to commit and pushing. So commit the files and then push.

Answer 29

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.)

Answer 30

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

Answer 31

Short answer: This error means the branch you want to push in remote doesn't exist!

In my case, starting from October-2020, the repos created since then had the main branch instead of the previous master branch. So all I had to do 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! Hope that helps! Happy coding!

Answer 32

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

Answer 33

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.

Answer 34

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 correct branch name.

command below worked for me

git push origin main

Answer 35

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

Answer 36

This will also happen if you have a typo in the branch name you're trying to push.

Answer 37

git add .

is all you need. That code tracks all untracked files in your directory.

Answer 38

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.

Answer 39

You need to configure your Git installation if it is the first time that you use it, with:

git config --global user.email "you@example.com"

git config --global user.name "Your Name"

Answer 40

In end of 2020, GitHub changed its master branch to main branch

I noticed GitHub created a new branch master and this 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 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

Answer 41

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.

Answer 42

git push -u origin master

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 are no commits in the repository and thus no master branch to push to the server.

It worked for me

Resolution

1) git init
2)git commit -m "first commit"
3)git add app
4)git commit -m "first commit"
5)git push -u origin master

Answer 43

Github changed the default branch name from master to main. So if you created the repo recently, try pushing main branch

git push origin main

Github Article

Answer 44

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

Answer 45

This error occurs as you are trying to push an empty repo into the git server. This can be mitigated by initializing a README.md file :

cat > README.md

Then type something, followed by an enter, and a CTRL+D to save. Then the usual committing steps :

git add .
git commit -m "Initial commit"
git push origin master

Answer 46

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

Answer 47

Try this:

git add .

git commit -m "your commit message"

git remote add origin *remote repository URL*

git push origin *your-branch-name*

Answer 48

Only commit solved this error:

git commit -m "first commit"

Answer 49

This worked for me, resetting to remote master the repository:

git checkout master
git commit -a -m "your comment"
git push origin master

Answer 50

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>>.

Answer 51

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"

Answer 52

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

Answer 53

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.

Answer 54

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

Answer 55

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

Answer 56

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 repo link here"
git push -u origin master

Thanks. Hope it helps.

Answer 57

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

Answer 58

Check your commit title, because if you forget the git commit -m "xxxx" command, you get the same problem

git commit -m "initial commit"

Answer 59

I ran into the same snag..and the solution was to push the code to the repo 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

Answer 60

First of all make sure that you are using master branch. In my case branch was main instead of master. So what I did was

git push origin main

You can see the result in this photo

Answer 61

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.

Answer 62

As one of the options for solving your problem:

git push origin HEAD

Answer 63

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.

Answer 64

I had a similar error. But Git tells me:

*** Please tell me who you are.

Run

git config --global user.email "you@example.com"
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.

Answer 65

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

Answer 66

Maybe GitHub doesn't know who you are.

First you have to run:

git config --global user.email "you@example.com"
git config --global user.name "Your Name"

Answer 67

Try git show-ref

You might see refs/heads/live

This means you should do

git push -u origin live

Answer 68

I forgot to commit then ran to this. JUST COMMIT

Answer 69

One reason for this month is probably be: github has rename default "master" branch to "main" branch. So, use git push origin main instead.

Answer 70

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

Answer 71

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)

Answer 72

For Repositories WIKI, I encountered this error also.

git show-branch

if shows master then

git push -u origin master

Answer 73

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

Answer 74

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.

Answer 75

I had the same issue and fixed it using the following steps:

• git pull --rebase https://github.com/yours master
• git add .
• git commit -m 'commit message'
• git push origin master

Answer 76

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.

Answer 77

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".

Answer 78

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.

Answer 79

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 ...

Answer 80

You may run into this issue for multiple reasons.

1. Pending commit for the stagged 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 name of branch,(i.e mster instead of master) then it ill lead you to this error. means the branch you're trying to push into is not in the local repository.

Answer 81

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.

Answer 82

I had faced 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.

Answer 83

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

Answer 84

I faced this exact problem while dealing with VCS in Android Studio. It turns out all I had to do was:

1. Select all files from the "app" folder;
2. Go to VCS (Option at top);
3. "Add" the files;
4. Committing again via terminal, or by clicking via the drop down menu, and;
5. Push!

Eureka! :D

Answer 85

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

Answer 86

I faced 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

Answer 87

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

Answer 88

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

Answer 89

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

Answer 90

For users of Bash within Cmder on Windows, make sure to create a new .ssh folder in your new home directory.

1. Go to your home directory cd ~.

2. Generate ssh keys ssh-keygen.

3. Leave all inputs blank (keep pressing enter)

4. Copy the id_rsa.pub file into your Github > Settings > SSH Keys

Answer 91

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

Answer 92

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 "you@example.com"
 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

Answer 93

If you have Visual Studio Code:

1. Delete .git folder if you don’t need changes to track (if yes, git stash)
2. git init
3. git commit -m "first commit"
4. git remote add origin https://github.com/YOURusername/YOURrepo.git
5. By Visual Studio Code UI IDE, GOTO source control from the left hand side panel or (Ctrl + Shift + G)
6. Stage all your changes or part
7. Commit your changes
8. Synchronize your changes by left bottom button (like number or like cloud icon). Then Visual Studio Code wants you to enter your username and password.

If 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

Answer 94

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!!

Answer 95

March 2021, with Git 2.31:

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.

Answer 96

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.

Answer 97

For Gitlab users, updated version of gitlab will now have 'main' branch as default.

So you can try the following:

git push origin main

Reference: Gitlab new git default branch name is main

Answer 98

Recently came across this problem, what I did was I checked show-ref using, git show-ref and checked whether

refs/heads/master

was present.

It was present, 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.

Answer 99

None of the above solutions worked for me when I got the src-refspec error.

My workflow:

• pushed to remote branch (same local branch name)
• deleted that remote branch
• changed some stuff & committed
• pushed again to the same remote branch name (same local branch name)
• got src-refspec error.

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.)

Answer 100

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.

Answer 101

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.

Answer 102

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.

Answer 103

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

Answer 104

If you are using Git Bash on Windows, try restarting it. It worked for me!

Answer 105

Permissions issue? Resolution: fork it

I got this error because I had no 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.

Answer 106

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>)

Answer 107

I think this might help someone. I made my first major commit today. I tried a lot of the guide given it kept spitting errors.

First: cd into the directory with your files Initialize git: git init commit the files: git commit To enforce the commit if there are any hazy bash commands: click 'I' to insert your commit message To continue: click 'ESC'

To send to your github repo first ensure that your username and email has been added:

git config --global user.name 'Your name'
git config --global user.email 'name@mail.com'

Continue:

git remote add origin https://github repo url

To push to the repo:

git push -u origin 'https://github.repo url'

It loads the commits to your repository. DONE!!!

Answer 108

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 anymore errors!

Answer 109

1. git branch

2. Rename the branch with -mv flag:

   git branch -mv origin master

After this git branch should show master

Answer 110

Make sure you do not have invisible typo in a branch name:

$ git branch
master
* <U+0096>your_branch_name

There is a invisible <U+0096> character which probably got there by pasting branch name. Rename your current branch to correct value and then try push again:

$ git branch -m your_branch_name

Answer 111

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.

Answer 112

git init

first command first.. first we need to initialize // and this should work for sure!...

Answer 113

git init git add . git commit -m "message" prompt me to enter email and user name git config --global user.email "you@example.com" git config --global user.name "Your Name" After enter above details committed files and pushed successfully.

git push

Answer 114

Initially every file is in untracked state. We need to add untracked files from the working directory to the staging area, only then git will 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. What you did is, 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 than follow this steps.

git init

git add .

git commit -m "First commit"

Answer 115

I think the problem stems from adding and committing your node_modules folder.

When you use git add ., do you 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 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.

Answer 116

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.

Answer 117

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

Answer 118

In my case error occurred when I was pushing changes to the branch which I only had locally. Remote branch was not existed with the same name. I resolved error with following command:

git push --set-upstream origin "your-branch-name"

Answer 119

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!

Answer 120

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

Answer 121

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 masters and it worked.

NB: Check to ascertain if the primary branch is main or master.

As of 2022

Answer 122

I had an extremely long local branch name.

git branch -m new_shorter_branch_name

fixed the problem.

Answer 123

I tried this :

git push -u origin master

and it's working by my side.