bloom fails to push to release repo with --new-track

[nlamprian]

I tried releasing a new package for ROS 2.

bloom-release --new-track --rosdistro humble --track humble gazebo_video_monitors

After preparing the master branch, bloom fails to push (I have indeed configured my oauth token):

==> git push --dry-run
fatal: The current branch master has no upstream branch.
To push the current branch and set the remote as upstream, use

    git push --set-upstream origin master

Cannot push to remote release repository.

Then, I decided to copy the working clone of the release repo and push the branch myself.

After doing that, I reran bloom

bloom-release --rosdistro humble --track humble gazebo_video_monitors

The release was successfully carried out without being asked for credentials (ros/rosdistro#38952).
I can provide the logs if necessary.

(Meanwhile, with the same process for noetic, I was asked multiple times for user/pass(token), even though ~/.config/bloom is in place.)

OS: Ubuntu 22.04.3
bloom: python3-bloom 0.11.2-100

[christian-rauch]

I am encountering the same issue with --new-track on an empty release repo. "Empty" meaning here that the remote has no branch and a git clone https://github.com/ros2-gbp/<package>-release.git will return warning: You appear to have cloned an empty repository..

One simple workaround is to create an empty README.md file via the GitHub web interface before running bloom-release --new-track.