git error: failed to push some refs to remote

[SuperJUNOed]

Select Topic Area

Question

Body

I can't push now, though I could do it yesterday.

When I use git push origin master, I get an error:
`
$ git remote -v
origin https://github.com/REDACTED.git (fetch)
origin https://github.com/REDACTED.git (push)

$ git push origin master
Username for 'https://github.com': REDACTED
Password for 'https://[email protected]':
To https://github.com/REDACTED.git
! [rejected] master -> master (non-fast-forward)
error: failed to push some refs to 'https://github.com/REDACTED.git'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.`

[jge162]

Hello @SuperJUNOed .

• To resolve this issue, you should first run git pull origin master to update your local branch with the changes from the remote branch.

• After resolving any conflicts that may arise during the merge, you should be able to push your changes to the remote branch using git push origin master.

[conceptfac]

fatal: couldn't find remote ref master

[s-spoon]

And you can rename existing repository default branch from master to main.
The rest of this 2014 answer has been updated to use "main")

(The following assumes github.com itself is not down, as eri0o points out in the comments: see www.githubstatus.com to be sure)

If the GitHub repo has seen new commits pushed to it, while you were working locally, I would advise using:

git pull --rebase
git push

The full syntax is:

git pull --rebase origin main
git push origin main

With Git 2.6+ (Sept. 2015), after having done (once)

git config --global pull.rebase true
git config --global rebase.autoStash true

A simple git pull would be enough.
(Note: with Git 2.27 Q2 2020, a merge.autostash is also available for your regular pull, without rebase)

That way, you would replay (the --rebase part) your local commits on top of the newly updated origin/main (or origin/yourBranch: git pull origin yourBranch).

See a more complete example in the chapter 6 Pull with rebase of the Git Pocket Book.

I would recommend a:

add and commit first

git push -u origin main

Or git 2.37 Q2 2022+

git config --global push.autoSetupRemote true
git push

That would establish a tracking relationship between your local main branch and its upstream branch.
After that, any future push for that branch can be done with a simple:

git push

Again, with Git 2.37+ and its global option push.autoSetupRemote, a simple git push even for the first one would do the same (I.e: establishing a tracking relationship between your local main branch and its upstream branch origin/main).

Since the OP already reset and redone its commit on top of origin/main:

git reset --mixed origin/main
git add .
git commit -m "This is a new commit for what I originally planned to be amended"
git push origin main

There is no need to pull --rebase.

Note: git reset --mixed origin/main can also be written git reset origin/main, since the --mixed option is the default one when using git reset.

[gokuthecoder]

thank you sir

[RobQuistNL]

It seems like right now there might be some issues on Github that cause these issues. I've seen errors regarding pushing, but then the commit actually did make it in the repository.

The actions also seem to be broken - I see no status or information about them.

https://www.githubstatus.com/ shows some issues;

https://downdetector.com/status/github/

[tochman]

Great. So it's not just me 🥲

[almahdi404]

In my case commits are being pushed to github.
git clone does include the pushed commits but they aren't visible in the repository.

[ruk93]

Having same experience as @almahdi404 mentioned.

[brenicolas]

experiencing the same issue @almahdi404

[ntruc710i]

git pull --rebase origin main

git push -u origin main

[RajeshMoravaneni7]

It did work for me. Thank You

[Jesusson-softwareandIT]

Wow guy you put the p in programmer. Nice one. Works

[Sudhanshu-273]

I got the same error, The reason behind it was, I exposed one of my API keys in a working file, I moved it to env, and it worked for me.