DEV Community

Simplify pushing to git

Michal Bryxí on October 04, 2018

I think everyone using git from command line knows this scenario: 1) Code, code, code, ... 2) Hmm, better save my progress. $ git checkout -b my...

Read full post

Alexis Reigel • Oct 8 '18

And then you just have to manually type the lengthy command above to be able to push.

Instead of having to type git push --set-upstream origin myawesomefeature the following shorter version works as well (i.e. the branch name can be omitted, it defaults to the current one, and the flag --set-upstream has a short version -u):

git push origin -u

John Paul Grefaldo • Apr 11 '19

I'm afraid that didn't work for me.

Alexis Reigel • Apr 12 '19

Can you elaborate a bit? What's the error message?

John Paul Grefaldo • Apr 12 '19

same as above post,

$ git push
fatal: The current branch myawesomefeature has no upstream branch.
To push the current branch and set the remote as upstream, use

    git push --set-upstream origin myawesomefeature

Alexis Reigel • Apr 12 '19

I'm confused. That error is expected if you just issue git push. My suggestion was to use git push origin -u (instead of the longer version git push --set-upstream origin myawesomefeature).

John Paul Grefaldo • Apr 13 '19 • Edited

Sorry I've no idea, I've tried.

when

git config --global push.default upstream

what's your config?

John Paul Grefaldo • Apr 13 '19

From what I understand, I think it will only work if it was push successfully before or branch exist in remote?

ref: git-scm.com/docs/git-push#Document...

Alexis Reigel • Apr 15 '19

what's your config?

I haven't set that config, I use the default (i.e. push.default=simple). For me git push origin -u works.

Setting git config --global push.default upstream I get the same error as you.

The OP suggested to use git config --global push.default current though, which has the desired effect (i.e. git push sets the remote branch as the tracking branch).