-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upload to Ansible Galaxy into "tunfish" namespace #3
Comments
Dear Anton, apologies, I just permitted full administrative permissions on this repository to you and also authorized Ansible to access the tunfish organization on GitHub. With kind regards, |
I tried to follow the documenation you mentioned but only was able to import the GitHub repository as a role into my own namespace (amotl) at [1] (deleted again). Apparently I don't have access to the "tunfish" namespace yet. Maybe you can take over from here or, the other way round, permit access permissions of the "tunfish" namespace on Ansible Galaxy [2] to me? [1] https://galaxy.ansible.com/amotl/ansible_wireguard |
i was able to set you as owner at the galaxy namespace byside of me. you should no be able to upload the role via github, following the given documentation |
Thanks for the reminder, but it sadly seems you did not checked the documentation of the ansible galaxy.
https://galaxy.ansible.com/docs/contributing/importing.html#importing-roles
the easiest way to import the role to the galaxy is giving galaxy access via the tunfish organization to the repo,
it is also possible to trigger new imports via travis-ci, i think github actions would work in the feature to.
since i'm only an outside collaborator for this repository i do not have any permissions to do so.
The text was updated successfully, but these errors were encountered: