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
ansible-lint #283
Comments
I do use ansible lint but have not used it in this project. Just running --fix might change more then needed. But if you feel up to it you could also just run it, make a PR see if the changes are solid.. unless @guenhter has some time? |
When we run this and make everything linted, do you think it would be worth add this to the CI pipeline so that future PR's always fail in case they are not linted? |
That would make sense yes.. a PR could have a check for that. |
Once you achieve no errors, it is worth adding it to CI. |
@guenhter Thx for some progress. |
@abielan At the moment, I'm very busy and don't have much time for this. But feel free to tackle a few of the linter issues and submit it as PR. I'm happy to review and merge that then in a timely manner. |
Seems this message did not get a lot of love. This does not mean it was not seen but time wise might not have made it to proper attention. This is just the clean up action ;) |
Please, update syntax to be compatible with ansible-lint.
Use of
ansible-lint --write
will be huge and fast step. :-)I assume that, as the author, you will quickly check whether anything has been broken by the machine.
The text was updated successfully, but these errors were encountered: