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

**URL:** <https://forum.ansible.com/t/what-is-the-purpose-of-the-branch-on-galaxy-role-import/1974>\
**Category:** Get Help\
**Tags:** galaxy-ng\
**Created:** [October 26, 2023, 10:35am UTC](https://forum.ansible.com/t/what-is-the-purpose-of-the-branch-on-galaxy-role-import/1974 "2023-10-26T10:35:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![L3D](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/l3d/32/911_2.png) [@L3D](https://forum.ansible.com/u/L3D)\
**Post date:** [October 26, 2023, 10:35am UTC](https://forum.ansible.com/t/what-is-the-purpose-of-the-branch-on-galaxy-role-import/1974/1 "2023-10-26T10:35:07Z")

</div>

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](https://us1.discourse-cdn.com/ansible/original/2X/a/a1813c83f51ff47b31fb9c265f74baf2711da0fa.png)](https://galaxy.ansible.com/ui/standalone/roles/roles-ansible/test/)

I created a github action to import ansible-roles to galaxy-ng: [Action Ansible Galaxy Release · Actions · GitHub Marketplace · GitHub](https://github.com/marketplace/actions/action-ansible-galaxy-release)

And I noticed, the string in the “–branch” version is used as version. So I changed the --branch to use the current release tag.  
But now I am curious, dear ansible-galaxy experts. Is this the intended mechanism? Wouldn’t it be much more logical to call this option something else like --branch? For example --tag or --version?  
Have I fundamentally misunderstood something about the galaxy role import tooling?

Thank you for your answers 😘