-
Notifications
You must be signed in to change notification settings - Fork 35
Use galaxy-importer in our CI pipeline #167
Copy link
Copy link
Open
Labels
0 - TriagingIssue is accepted, but a milestone has yet to be added for the issue.Issue is accepted, but a milestone has yet to be added for the issue.Build AutomationIssues for changes to the build system, without functional changes needed to the project.Issues for changes to the build system, without functional changes needed to the project.NO RELEASE NOTESShould not be included in the release notes - not enhancing or fixing end product.Should not be included in the release notes - not enhancing or fixing end product.
Description
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
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
0 - TriagingIssue is accepted, but a milestone has yet to be added for the issue.Issue is accepted, but a milestone has yet to be added for the issue.Build AutomationIssues for changes to the build system, without functional changes needed to the project.Issues for changes to the build system, without functional changes needed to the project.NO RELEASE NOTESShould not be included in the release notes - not enhancing or fixing end product.Should not be included in the release notes - not enhancing or fixing end product.