Skip to content

ansible-lint checks playbooks for practices and behavior that could potentially be improved and can fix some of the most common ones for you

License

Notifications You must be signed in to change notification settings

ansible/ansible-lint

Use this GitHub action with your project
Add this Action to an existing workflow or create a new one
View on Marketplace

Folders and files

NameName
Last commit message
Last commit date
Mar 27, 2023
Mar 24, 2023
Feb 14, 2023
Feb 11, 2023
Mar 16, 2023
Mar 24, 2023
Jan 17, 2023
Mar 27, 2023
Mar 27, 2023
Mar 4, 2023
Feb 23, 2023
Feb 11, 2023
Dec 2, 2022
Feb 9, 2023
Jan 18, 2023
Apr 17, 2020
Jan 26, 2023
Feb 9, 2023
Feb 9, 2023
Mar 27, 2023
Nov 17, 2022
Feb 17, 2022
Dec 2, 2022
Feb 9, 2023
Feb 15, 2023
Feb 14, 2022
Feb 17, 2022
Nov 30, 2022
Mar 27, 2023
Dec 14, 2022
Mar 3, 2022
Feb 17, 2023
Dec 31, 2022
Mar 16, 2023
Sep 30, 2022
Mar 24, 2023
Mar 14, 2023

Repository files navigation

PyPI version Ansible-lint rules explanation Discussions GitHub Actions CI/CD Language grade: Python pre-commit

Ansible-lint

ansible-lint checks playbooks for practices and behavior that could potentially be improved. As a community backed project ansible-lint supports only the last two major versions of Ansible.

Visit the Ansible Lint docs site

Contributing

Please read Contribution guidelines if you wish to contribute.

Licensing

The ansible-lint project is distributed as GPLv3 due to use of GPLv3 runtime dependencies, like ansible and yamllint.

For historical reasons, its own code-base remains licensed under a more liberal MIT license and any contributions made are accepted as being made under original MIT license.

Authors

ansible-lint was created by Will Thames and is now maintained as part of the Ansible by Red Hat project.