Re: git push refspec to specify tracking branch

From: Avery Pennarun <apenwarr@gmail.com>
Date: Mar 31, 2010, 03:24 UTC
Message-ID: <32541b131003302024n42994e3nddab7544c24f93bd@mail.gmail.com>
In-Reply-To: <5D7B2F13-760B-4EBE-93A4-06B9CDDC3976@sb.org>

On Tue, Mar 30, 2010 at 10:24 PM, Kevin Ballard <kevin@sb.org> wrote:

Show 8 quoted lines

> On Mar 30, 2010, at 6:19 PM, Avery Pennarun wrote:
>> git push origin localbranchname:remotebranchname
>
> Yes that works, but it's annoying to type out every time, especially when my
> branch has a long name and I don't want to risk typos. Even worse, the
> tab-completion in bash uses `git ls-remote` to complete the remote part of
> refspecs, so it's even slower to type "foo:kba<tab>" than it is to type
> "foo:kballard/foo".

You might consider creating a separate 'remote' entry then in your .git/config. You should be able to reconfigure the refspec on that one to use a particular branch name instead of a wildcard. It's not exactly pretty, but laziness will be laziness.

A similar option would be to just make a shell alias and be done with it:

savebranch()
{
    git push origin $1:kballard-$1
}

Have fun,

Avery