From: Cliff Schomburg Date: Mon, 03 Jun 2019 21:34:26 GMT Subject: RE: Simple shortcut for "git push --set-upstream origin newBranchName" Message-ID: 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. Thanks,m Cliff -----Original Message----- From: Cliff Schomburg Sent: Friday, May 31, 2019 11:13 AM To: Patryk Obara ; git@vger.kernel.org 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 ; git@vger.kernel.org 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: https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit-scm.com%2Fdocs%2Fgit-config%23Documentation%2Fgit-config.txt-pushdefault&data=02%7C01%7Cclisc%40microsoft.com%7Cf52d699c3fc149d20de508d6e5d96a4c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636949119289770838&sdata=K2NezwOWzZrqsU7l8GybjbJuwmRnC2llT77UhvF%2B8RU%3D&reserved=0 -- Patryk Obara