Skip to main content
← Back to workflows

How to use Ansible-lint with GitHub Actions?

ansible/ansible-lint -
GitHub Action
v24.5.0
3,455
Contributors
Contributor - ssbarneaContributor - webknjazContributor - willthames
Categories
CICUBE ANALYTICS INSIGHTS
Engineering Velocity: 25% Team Time Lost to CI Issues
View Platform →
3.5h
Time Saved/Dev/Week
40%
Faster Releases
Click for next insight
Usage
name: ansible-lint
on:
pull_request:
branches: ["main", "stable", "release/v*"]
jobs:
build:
name: Ansible Lint
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Run ansible-lint
uses: ansible/ansible-lint@main

ansible-lint logo

ansible-lint

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


How to use use Ansible Lint with GitHub action?

Ansible-lint GitHub action checks our playbooks for practices and behaviors that could potentially be improved.

Why Use Ansible-lint?

  • Community Support: It's supported by the community and compatible with the last two major versions of Ansible, making it quite reliable.
  • Documentation: There’s comprehensive documentation available which can be accessed on the Ansible Lint documentation site.

We can integrate Ansible-lint directly into our GitHub Actions workflow. This integration allows us to automatically check any changes in our playbooks without the need to install Ansible-lint locally.

Potential Benefits:

  • Quality Assurance: Ensures that our playbooks are up to standard before they are merged, reducing the likelihood of errors.
  • Efficiency: Automates the review process for playbook standards, saving us time during code reviews.