Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use galaxy-importer in our CI pipeline #167

Open
2 tasks done
vexx32 opened this issue Oct 1, 2024 · 0 comments
Open
2 tasks done

Use galaxy-importer in our CI pipeline #167

vexx32 opened this issue Oct 1, 2024 · 0 comments
Labels
0 - _Triaging Issue is accepted, but a milestone has yet to be added for the issue Build Automation Issues for changes to the build system, without functional changes needed to the project NO RELEASE NOTES Should not be included in the release notes - not enhancing or fixing end product

Comments

@vexx32
Copy link
Member

vexx32 commented Oct 1, 2024

Checklist

  • I have verified this is the correct repository for opening this issue.
  • I have verified no other issues exist related to my request.

Is Your Feature Request Related To A Problem? Please describe.

As we can see in #163, the import checks on Automation Hub do come back with linting warnings.

Describe The Solution. Why is it needed?

In one case, one of the warnings was apparently enough to reject the publishing of the collection, so we should look to be running the same checks ourselves, in order to avoid surprises.

In talking with RedHat folks, it looks like we would want to run https://github.com/ansible/galaxy-importer as a CI step during our testing.

Additional Context

No response

Related Issues

No response
@vexx32 vexx32 added Build Automation Issues for changes to the build system, without functional changes needed to the project 0 - _Triaging Issue is accepted, but a milestone has yet to be added for the issue NO RELEASE NOTES Should not be included in the release notes - not enhancing or fixing end product labels Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
0 - _Triaging Issue is accepted, but a milestone has yet to be added for the issue Build Automation Issues for changes to the build system, without functional changes needed to the project NO RELEASE NOTES Should not be included in the release notes - not enhancing or fixing end product
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vexx32