mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Cliff Schomburg <>
To: Patryk Obara <>,
	"" <>
Subject: RE: Simple shortcut for "git push --set-upstream origin newBranchName"
Date: Mon, 3 Jun 2019 21:34:26 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

So I gave this a try and it seems not to be behaving as expected:

>git push -u
fatal: The current branch {branchName} has no upstream branch.
To push the current branch and set the remote as upstream, use

    git push --set-upstream origin {branchName}

I'm using Git for Windows in a Windows CMD prompt, if that matters at all.


-----Original Message-----
From: Cliff Schomburg 
Sent: Friday, May 31, 2019 11:13 AM
To: Patryk Obara <>;
Subject: RE: Simple shortcut for "git push --set-upstream origin newBranchName"

Thanks, Patryk.  It's always nice to see the feature I want is already implemented!  😊

-----Original Message-----
From: Patryk Obara <> 
Sent: Friday, May 31, 2019 11:05 AM
To: Cliff Schomburg <>;
Subject: Re: Simple shortcut for "git push --set-upstream origin newBranchName"

On 31/05/2019 16:56, Cliff Schomburg wrote:
> Wow, I did not see that in the man pages... but I see it now.  Thanks!
> So I guess I would change my ask to this:
> "git push -u"
> Should default to "origin branch" if no parameters are provided.

I think most people will agree, considering it already works this way :)

The default behaviour of git push changed in Git 2.0, perhaps you were reading some old tutorial. You can configure it to match your preferences by changing push.default value in your git config:;;sdata=K2NezwOWzZrqsU7l8GybjbJuwmRnC2llT77UhvF%2B8RU%3D&amp;reserved=0

Patryk Obara

  reply	other threads:[~2019-06-03 21:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
     [not found]   ` <>
2019-05-31 14:45     ` Simple shortcut for "git push --set-upstream origin newBranchName" Cliff Schomburg
2019-05-31 14:51       ` Patryk Obara
2019-05-31 14:56         ` Cliff Schomburg
2019-05-31 15:05           ` Patryk Obara
2019-05-31 15:13             ` Cliff Schomburg
2019-06-03 21:34               ` Cliff Schomburg [this message]
2019-05-31 15:11           ` Denton Liu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).