I created a new project following the instructions on the new project git tab.

Then:

~/Sites/_sandbox/content_push joachim$ git push origin master
Counting objects: 7, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (7/7), done.
Writing objects: 100% (7/7), 4.40 KiB, done.
Total 7 (delta 0), reused 0 (delta 0)
To joachim@git.drupal.org:project/content_push.git
 * [new branch]      master -> master
~/Sites/_sandbox/content_push joachim$ git checkout -b 6.x-1.x
Switched to a new branch '6.x-1.x'
~/Sites/_sandbox/content_push joachim$ git push origin 6.x-1.x 
Total 0 (delta 0), reused 0 (delta 0)
fatal: bad revision '^{master}'
To joachim@git.drupal.org:project/content_push.git
 * [new branch]      6.x-1.x -> 6.x-1.x
~/Sites/_sandbox/content_push joachim$ 

Comments

joachim’s picture

And now this happens:

~/Sites/_sandbox/content_push joachim$ git push origin 6.x-1.x 
Counting objects: 5, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 610 bytes, done.
Total 3 (delta 2), reused 0 (delta 0)
To joachim@git.drupal.org:project/content_push.git
   62f1be2..488f9dc  6.x-1.x -> 6.x-1.x
~/Sites/_sandbox/content_push joachim$ git push
fatal: The current branch 6.x-1.x is not tracking anything.
~/Sites/_sandbox/content_push joachim$ 

joachim’s picture

... and yet my commit appears on d.org !?!?!

joachim’s picture

I cloned onto another machine and the branch didn't appear. Trying to create it got me this when I pushed:

~/Sites/_sandbox/form_email_confirmation joachim$ git push origin 6.x-1.x
Total 0 (delta 0), reused 0 (delta 0)
fatal: bad revision '^{master}'
To joachim@git.drupal.org:project/form_email_confirmation.git
* [new branch] 6.x-1.x -> 6.x-1.x

eliza411’s picture

Status: Active » Postponed

There's a fix for this, but there is no adequate environment for testing the fix before deployment and no actual deployment process. Since it's ugly and confusing, but it doesn't actually break anything, this is postponed until there's a reasonable procedure in place.

rfay’s picture

Status: Postponed » Active

This is easy enough to demonstrate, so marking it active. #1075506: fatal: bad revision '^{master}' when pushing a branch (duplicate of this one) has instructions on how to recreate.

eliza411’s picture

Priority: Critical » Normal

@rfay I'm guessing after a year this probably isn't critical; any idea if this is still happening?

rfay’s picture

It never was critical, as it was a bogus error message.

I'd be surprised if it got fixed, but I haven't seen it lately.