Skip to main content

PyPI version Ansible-lint rules explanation Discussions 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

Using ansible-lint as a GitHub Action

This action allows you to run ansible-lint on your codebase without having to install it yourself.

# .github/workflows/ansible-lint.yml
name: ansible-lint
on:
  pull_request:
    branches: ["main", "stable", "release/v*"]
jobs:
  build:
    name: Ansible Lint # Naming the build is important to use it as a status check
    runs-on: ubuntu-24.04
    steps:
      - uses: actions/checkout@v4
      - name: Run ansible-lint
        uses: ansible/ansible-lint@main
        # optional (see below):
        with:
          args: ""
          setup_python: "true"
          working_directory: ""
          requirements_file: ""

All the arguments are optional and most users should not need them:

  • args: Arguments to be passed to ansible-lint command.
  • setup_python: If python should be installed. Default is true.
  • working_directory: The directory where to run ansible-lint from. Default is github.workspace. That might be needed if you want to lint only a subset of your repository.
  • requirements_file: Path to the requirements.yml file to install role and collection dependencies.

For more details, see ansible-lint-action.

Communication

Refer to the Talk to us section of the Contributing guide to find out how to get in touch with us.

You can also find more information in the Ansible communication guide.

Contributing

Please read Contribution guidelines if you wish to contribute.

Code of Conduct

Please see the Ansible Community Code of Conduct.

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.

Metadata

Release files for ansible-lint 24.12.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ansible-lint 24.12.2
File Size Uploaded
ansible_lint-24.12.2.tar.gz 548.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for ansible-lint 24.12.2
File Interpreter ABI Platform
ansible_lint-24.12.2-py3-none-any.whl Python 3 none any Details

Total release size: 858.7 kB

Release files / ansible_lint-24.12.2.tar.gz

Download URL ansible_lint-24.12.2.tar.gz
Size 548.0 kB
Tags Source
SHA-256 checksum
How to use checksums
f636309c4e7f724fc1a544df529c4c2354f54cf35ede11d750366afb1158a464
BLAKE2b-256 checksum
How to use checksums
7d52131fdc2305536a6482265dc2de01279cbb138716e86ead5c3d8357430695
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.0.1 CPython/3.12.8

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Dec 12, 2024.

Transparency log

Release files / ansible_lint-24.12.2-py3-none-any.whl

Download URL ansible_lint-24.12.2-py3-none-any.whl
Size 310.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ce7a783ce4f053a965e31f308cdb57554259052efea04b8491c9704f11095e54
BLAKE2b-256 checksum
How to use checksums
0b307b4c1038fb491438243a99bd3d65b2c2dd450b821617107fa5e3d0ad108f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.0.1 CPython/3.12.8

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Dec 12, 2024.

Transparency log

Release history Release notifications | RSS feed

26.9.0

2 release files

26.8.0

2 release files

26.6.0

2 release files

26.2.0

2 release files

26.1.1

2 release files

25.9.0

2 release files

25.8.2

2 release files

25.8.1

2 release files

25.8.0

2 release files

25.7.0

2 release files

25.6.1

2 release files

25.6.0

2 release files

25.5.0

2 release files

25.4.0

2 release files

25.1.3

2 release files

25.1.1

2 release files

25.1.0

2 release files

This release

24.12.2 This release

2 release files

24.9.2

2 release files

24.9.1

2 release files

24.9.0

2 release files

24.7.0

2 release files

24.6.1

2 release files

24.5.0

2 release files

24.2.3

2 release files

24.2.1

2 release files

6.22.2

2 release files

6.22.1

2 release files

6.21.1

2 release files

6.21.0

2 release files

6.20.2

2 release files

6.20.1

2 release files

6.20.0

2 release files

6.18.0

2 release files

6.17.2

2 release files

6.17.1

2 release files

6.17.0

2 release files

6.16.2

2 release files

6.16.1

2 release files

6.15.0

2 release files

6.14.6

2 release files

6.14.5

2 release files

6.14.3

2 release files

6.13.1

2 release files

6.13.0

2 release files

6.12.2

2 release files

6.11.0

2 release files

6.10.1

2 release files

6.10.0

2 release files

6.9.1

2 release files

6.9.0

2 release files

6.8.7

2 release files

6.8.6

2 release files

6.8.5

2 release files

6.8.4

2 release files

6.8.3

2 release files

6.8.2

2 release files

6.8.1

2 release files

6.8.0

2 release files

6.7.0

2 release files

6.6.1

2 release files

6.6.0

2 release files

6.5.2

2 release files

6.5.1

2 release files

6.5.0

2 release files

6.4.0

2 release files

6.3.0

2 release files

6.2.2

2 release files

6.2.1

2 release files

6.2.0

2 release files

6.1.0

2 release files

6.0.2

2 release files

6.0.1

2 release files

6.0.0

3 release files

5.4.0

2 release files

5.3.2

2 release files

5.3.1

2 release files

5.3.0

2 release files

5.2.1

2 release files

5.2.0

2 release files

5.1.3

2 release files

5.1.2

2 release files

5.1.1

2 release files

5.0.11

2 release files

5.0.10

2 release files

5.0.9

2 release files

5.0.8

2 release files

5.0.7

2 release files

5.0.6

2 release files

5.0.5

2 release files

5.0.4

2 release files

5.0.3

2 release files

5.0.2

2 release files

5.0.1

2 release files

5.0.0

2 release files

4.3.7

2 release files

4.3.6

2 release files

4.3.5

2 release files

4.3.4

2 release files

4.3.3

2 release files

4.3.2

2 release files

4.3.1

2 release files

4.3.0

2 release files

4.2.0

2 release files

4.1.0

2 release files

4.0.1

2 release files

4.0.0

2 release files

3.5.1

1 release file

3.5.0

1 release file

3.4.23

1 release file

3.4.22

1 release file

3.4.21

1 release file

3.4.20

1 release file

3.4.19

1 release file

3.4.18

1 release file

3.4.17

1 release file

3.4.16

1 release file

3.4.15

1 release file

3.4.13

1 release file

3.4.12

1 release file

3.4.11

1 release file

3.4.10

1 release file

3.4.9

1 release file

3.4.8

1 release file

3.4.7

1 release file

3.4.6

1 release file

3.4.5

1 release file

3.4.4

1 release file

3.4.3

1 release file

3.4.1

1 release file

3.4.0

1 release file

3.3.3

1 release file

3.3.2

1 release file

3.3.0

1 release file

3.2.5

1 release file

3.2.4

1 release file

3.2.3

2 release files

3.2.2

2 release files

3.2.1

2 release files

3.2.0

2 release files

3.1.3

2 release files

3.1.2

2 release files

3.1.1

2 release files

3.1.0

2 release files

3.0.1

2 release files

3.0.0

2 release files

2.7.1

1 release file

2.7.0

1 release file

2.6.2

1 release file

2.6.1

1 release file

2.5.0

1 release file

2.4.2

1 release file

2.4.1

1 release file

2.4.0

1 release file

2.3.9

1 release file

2.3.8

1 release file

2.3.6

1 release file

2.3.5

1 release file

2.3.3

1 release file

2.3.2

1 release file

2.3.1

1 release file

2.3.0

1 release file

2.2.0

1 release file

2.1.3

1 release file

2.1.0

1 release file

2.0.3

1 release file

2.0.1

1 release file

1.0.4

1 release file

1.0.3

1 release file

1.0.2

1 release file

1.0.1

1 release file

1.0.0

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page