bloom config is hardcoded to look at master branch new repositories use main as default about bloom HOT 4 OPEN

Another workaround available to maintainers is to sync main to master.

You can use this action to keep main and master in sync and bloom would use the synced version. https://github.com/zofrex/mirror-branch

I've used it here: https://github.com/osrf/rocker/blob/main/.github/workflows/mirror-main-to-master.yaml

from bloom.

Another workaround available to maintainers is to sync main to master.

I think this is probably more painful, and we can pretty easily figure out what the default branch is from git.

A command like: git ls-remote --symref origin HEAD should get the ref of origin that corresponds to the "default" branch on github.

from bloom.

We just had a chance to chat about this. We used to use use the bloom branch to be compatible with integration in a source repository but that quickly turned out to be not a good move. We moved to master for better visibility when viewing on github.

We would like to go back to using the bloom branch for clarity the use case. But doing that change is a bigger lift than we actively want to invest in this right now. Especially with supporting migration paths. So for now we are going to keep the standard that bloom relies on using the master branch.

When we deploy new ros2-gbp repositories via terraform it creates an empty repository that bloom will eventually push to. Github won't let us set the default branch until the branch is created. The default branch defaults to the first one pushed, which if bloom does it, will be master. If an individual pushes a branch such as main first it will become the default.

For now we should stick with the expectation that the default branch in a release repo should be master and if there's one created manually otherwise we will recommend manually changing it to master.

from bloom.

Places where people have run into problems:

• ros2-gbp/ros2-gbp-github-org#426
• ros/rosdistro#39536 (comment)

from bloom.