-
Notifications
You must be signed in to change notification settings - Fork 10
Fix/lint workflow 192 #199
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
Conversation
…ing workflow" This reverts commit 0510438.
Nice! That seems like it could really help a lot with development. |
We now have merged some major changes to the testing configuration. Could you please resolve the conflicts and have another look? |
I've looked through the workflows again and made some changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks again. This really will help with easier maintenance.
Fix NETWAYS#192. This PR introduces a reusable workflow. This general workflow handles the job necessary to run both `ansible-lint` and `yamllint` on **either** all roles or one specific role. All roles are linted when: - linting rules are changed - the linting workflow is changed Specific roles are linted when: - a role specific workflow is triggered (linting as first job) - the `full_stack` workflow is triggered (linting as first job) The workflow for the specific role now uses a call to the general linting workflow, while providing it with its own role name. This approach does not completely remove linting from single workflows, but it makes those linting jobs much more readable and reduces redundant code, while also allowing for a bit more flexibility. --------- Co-authored-by: Thomas Widhalm <[email protected]>
Fix #192.
This PR introduces a reusable workflow. This general workflow handles the job necessary to run both
ansible-lint
andyamllint
on either all roles or one specific role.All roles are linted when:
Specific roles are linted when:
full_stack
workflow is triggered (linting as first job)The workflow for the specific role now uses a call to the general linting workflow, while providing it with its own role name.
This approach does not completely remove linting from single workflows, but it makes those linting jobs much more readable and reduces redundant code, while also allowing for a bit more flexibility.