#3 new
Mike Nicholaides

`grb new` fails when the current branch has a dash in it

Reported by Mike Nicholaides | February 22nd, 2010 @ 01:10 PM

example output:

$ git branch master * old-branch

$ grb new newbranch git push origin oldbranch:refs/heads/newbranch
error: src refspec oldbranch does not match any.
error: failed to push some refs to 'git@github.com:...'
git fetch origin
git branch --track newbranch origin/newbranch
fatal: Not a valid object name: 'origin/newbranch'.
git checkout newbranch
error: pathspec 'newbranch' did not match any file(s) known to git.

Comments and changes to this ticket

  • webmat

    webmat February 22nd, 2010 @ 07:24 PM

    Thanks for the feedback.

    I'll see what I can do. I haven't updated git_remote_branch in an eternity, so don't hold your breath for now...

    I want to come back to it soon, I've got an ever-growing list of todo's for it -- I still use it regularly -- I'm just too busy to actually sit down for a few evenings to really give it the attention it deserves.

  • Mike Nicholaides

    Mike Nicholaides February 22nd, 2010 @ 08:14 PM

    No problem. I use it regularly, too, and love it.

    This bug isn't so bad because grb prints out the commands it's running, which made it easy to diagnose, and easy to run the commands myself.

    Keep up the good work,
    Mike

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

This is where you're welcome to whine about git_remote_branch

People watching this ticket

Pages