pre-commit-shfmt
ansible-lint
| pre-commit-shfmt | ansible-lint | |
|---|---|---|
| 1 | 11 | |
| 43 | 2,713 | |
| - | - | |
| 6.1 | 9.4 | |
| 2 months ago | about 2 years ago | |
| Python | Python | |
| - | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pre-commit-shfmt
ansible-lint
-
The Bullhorn #99 (Ansible Newsletter)
Ansible-lint version 6.14.6 is here, started using ruff linter along with 10+ bugfixes in this release.
-
The Bullhorn #95 (Ansible Newsletter)
Ansible-Devtools team made a new release of Ansible-Lint version 6.14.2 with couple of exciting bugfixes.
-
The Bullhorn #94 (Ansible Newsletter)
The Devtools team has released ansible-lint version 6.14.0, which includes 23 bugfixes and 3 minor changes. Please refer to the changelog here for more information.
-
The Bullhorn #93 (Ansible Newsletter)
ansible-lint 6.14 was released, dropping support for py38 and including over 25 changes and bugfixes.
-
The Bullhorn #92 (Ansible Newsletter)
Ansible-lint 6.13 introduces a new feature that allows users to utilize a .ansible-lint-ignore file. This file contains skip-rules that are loaded from the ignore file which is adjacent to the config file. Additionally, users can take advantage of the --generate-ignore argument to dump any current violations into an ignore file.
-
Open Source Collection of Ansible Good and Bad Practices
Cool, but ansible-lint and the official RedHat docs are a much better way to ensure you're using the official best practices. No offense, but stuff two random guys on Reddit threw together isn't a great resource for best practices.
-
ansible-lint 6.8.0b1 is out
Check https://github.com/ansible/ansible-lint/discussions/2534 for details and comment there if you detect any regressions.
-
Correct use of block: and when: (key-order)
There is more context here: https://github.com/ansible/ansible-lint/issues/578
-
The Bullhorn #69 (Ansible Newsletter)
ansible-lint 6.4.0 was released with lots of bugfixes and a new feature called "profiles", one that allow you to easily pick which set of rules you want to follow. https://github.com/ansible/ansible-lint/discussions/2254
-
What is your preferred software to write playbooks?
I use vanilla vim or nvim with checks from ansible-lint.
What are some alternatives?
shellcheck-py - python3/pip3 wrapper for installing shellcheck
ansible-vim - A vim plugin for syntax highlighting Ansible's common filetypes
ansible-language-server - 🚧 Ansible Language Server codebase is now included in vscode-ansible repository
ansible.scm - An ansible collection for prescriptive retrieval and publish using git
community.zabbix - Zabbix Ansible modules
coc-ansible - ansible-language-server extension for coc.nvim
jinja-docsite - A docsite for the Ansible community
conventional-pre-commit - A pre-commit hook that checks commit messages for Conventional Commits formatting
vyos.vyos - Ansible Network Collection for VyOS
ansible-snippets - Ansible Vim snippets
awx-operator - An Ansible AWX operator for Kubernetes built with Operator SDK and Ansible. 🤖
vscode-ansible - vscode/vscodium extension for providing Ansible auto-completion and integrating quality assurance tools like ansible-lint, ansible syntax check, yamllint, molecule and ansible-test.