This worked perfectly from the first attempt and now we do know that we don't need to wait for someone to remember to update ansible-lint recipe.
While we do have a pipeline that uses packit service to test that rpm packaging is not broken from incoming pull requests, we do not have any automated way to trigger RPM packaging an update for fedora when we release a new version.
Would it be possible to get a similar action that we can chain on our release pipeline?
--
Cheers,Sorin Sbarnea
Ansible DevTools Team Lead, Red Hat
_______________________________________________ packaging mailing list -- packaging@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to packaging-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/packaging@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue