Git push command, error encountered -fatal: invalid refspec 'https://github.......git'

Question

I'm in the master branch and have added the remote branch, after which I'm unable to push the data from local to remote.:

$ Git remote add master https://....git

$ Git push origin master https:// ...git
Fatal: invalid refspec 'https://...git'

Predicable

Answer 1

You should "git remote add" origin, not master:

git remote add origin https://...
git remote remove master
git push -u origin master

If you already add a remote origin, then fix it with git remote set-url, instead of git remote add:

git remote set-url origin https://...

Geer

I tried this. but I got the "error: remote origin already exists". How do I solve this ? – Lucic

@VedantKakade Good point. I have edited the answer to address that use case. – Geer

Answer 2

My problem was solved by changing the authentication method from HTTPS to SSH.

Guide for Github SSH keys: https://help.github.com/en/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent

Create a new SSH key in github (https://github.com/settings/keys)

Twelfthtide

Answer 3

I had similar problem with gitlab and what helped me in this case, was adding additional option --push-option=ci-skip and putting at the end HEAD:<branchname> like below

git checkout -b ${newbranch}
#..<do  your stuff>..
#..<add and commit>...
git push --push-option=ci-skip http://${SERVER_HOST}/${PROJECT_PATH}.git/ HEAD:${newbranch}

Everybody

Answer 4

I think I found a bug in git: Trying to push a branch that ends with ".lock" also fails with "invalid refspec":

git push --force-with-lease HEAD~21:refs/heads/add-cargo.lock
fatal: invalid refspec 'HEAD~21:refs/heads/add-cargo.lock'

git push --force-with-lease HEAD~21:refs/heads/add-cargo-lock
…
remote: Create a pull request for 'add-cargo-lock' on GitHub by visiting …
 * [new branch]            HEAD~21 -> add-cargo-lock

Other file extensions work, so this is a bit inconsistent. Git version 2.45.2.

Timpani