git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Cliff Schomburg <clisc@microsoft.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: RE: Simple shortcut for "git push --set-upstream origin newBranchName"
Date: Fri, 31 May 2019 14:45:05 +0000	[thread overview]
Message-ID: <BN8PR21MB1156F7F3E7EFF9C8A60F33D0B7190@BN8PR21MB1156.namprd21.prod.outlook.com> (raw)
In-Reply-To: <BN8PR21MB1156DA1893F64814F1BE8709B7180@BN8PR21MB1156.namprd21.prod.outlook.com>

Resending as plain text

From: Cliff Schomburg 
Sent: Thursday, May 30, 2019 6:29 PM
To: git@vger.kernel.org
Subject: Simple shortcut for "git push --set-upstream origin newBranchName"

Hi all,

This is more of a suggestion than a bug report.

I create new topic branches quite frequently and push them into the remote repo (origin).

It's a bit of a hassle to type "git push -set-upstream origin newBranchName" each and every time I want to push a new branch.

I'm proposing a shortcut for this command.  Perhaps "git push -default" or "git push -new-branch" which could be shortened to "git push -d" or "git push -nb" or something.

Based on the man-page for push, it looks like this could be an alias for:
    "git push -set-upstream origin HEAD"
In which case HEAD should always be the current branch name.

Thoughts?  Concerns?

Thanks,
Cliff


       reply	other threads:[~2019-05-31 14:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BN8PR21MB1156ED141AE2662BC5328A22B7180@BN8PR21MB1156.namprd21.prod.outlook.com>
     [not found] ` <BN8PR21MB1156F593DAEBD7194DA7041EB7180@BN8PR21MB1156.namprd21.prod.outlook.com>
     [not found]   ` <BN8PR21MB1156DA1893F64814F1BE8709B7180@BN8PR21MB1156.namprd21.prod.outlook.com>
2019-05-31 14:45     ` Cliff Schomburg [this message]
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
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=BN8PR21MB1156F7F3E7EFF9C8A60F33D0B7190@BN8PR21MB1156.namprd21.prod.outlook.com \
    --to=clisc@microsoft.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

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

	https://80x24.org/mirrors/git.git

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).