Role import from GitHub results in "master" release, not the tag release, breaking installs

[L3D]

I figured out, the --branch option is used for the galaxy-ng version. So if you are on your latest release tag on the main or master branch, you can run:

ansible-galaxy role import \
  --api-key <GalaxyAPIKey> \
  --branch <YourGitReleaseTag> \
  github_username github_repo

I created a github action, that can import new ansible role release with the correct set version to galaxy.ng: Action Ansible Galaxy Release · Actions · GitHub Marketplace · GitHub
It is using the GITHUB_REF_NAME enviroment variable as version name.

I created a post about this topic here:

What is the purpose of the --branch on galaxy role import

Hello all, Now that showing the version on galaxy-ng is working again, I am a bit confused. Because my imported roles suddenly have the option “main” several times. This can be seen, for example, in the test role roles-ansible.test that I made to test the import on galaxy-ng in more detail: [image] I created a github action to import ansible-roles to galaxy-ng: Action Ansible Galaxy Release · Actions · GitHub Marketplace · GitHub And I noticed, the string in the “–branch” version is used as…