RE: Simple shortcut for "git push --set-upstream origin newBranchName"

From: Cliff Schomburg <clisc@microsoft.com>
Date: May 31, 2019, 15:13 UTC
Message-ID: <BN8PR21MB1156D785177A40EA7D8341ABB7190@BN8PR21MB1156.namprd21.prod.outlook.com>
In-Reply-To: <ebc03b4e-daf8-d47f-94ca-a4a549589773@gmail.com>

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

-----Original Message-----
From: Patryk Obara <dreamer.tan@gmail.com> 
Sent: Friday, May 31, 2019 11:05 AM
To: Cliff Schomburg <clisc@microsoft.com>; git@vger.kernel.org
Subject: Re: Simple shortcut for "git push --set-upstream origin newBranchName"

On 31/05/2019 16:56, Cliff Schomburg wrote:

Show 7 quoted lines

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

https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit-scm.com%2Fdocs%2Fgit-config%23Documentation%2Fgit-config.txt-pushdefault&amp;data=02%7C01%7Cclisc%40microsoft.com%7Cf52d699c3fc149d20de508d6e5d96a4c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636949119289770838&amp;sdata=K2NezwOWzZrqsU7l8GybjbJuwmRnC2llT77UhvF%2B8RU%3D&amp;reserved=0

-- Patryk Obara