GitHub Actions

The official Action wraps the install.sh flow plus alint invocation into one step.

Inline PR annotations (default)

- uses: asamarts/alint@v0.9.20

This runs alint check --format github against . and emits findings as ::error:: / ::warning:: workflow commands, which GitHub renders inline on the PR.

Inputs (all optional)

- uses: asamarts/alint@v0.9.20
  with:
    version: v0.9.20        # alint release tag (default: latest)
    path: .                # directory to lint (default: .)
    format: github         # human | json | sarif | github (default)
    config: |              # extra config path(s), one per line
      .alint.yml
    fail-on-warning: false
    args: ""               # extra CLI args appended verbatim

Upload findings to GitHub Code Scanning

Use format: sarif and pipe to the standard upload action:

- uses: asamarts/alint@v0.9.20
  id: alint
  with:
    format: sarif
  continue-on-error: true
- uses: github/codeql-action/upload-sarif@v3
  if: always()
  with:
    sarif_file: ${{ steps.alint.outputs.sarif-file }}

continue-on-error: true is what lets the SARIF upload run even when alint finds issues — without it, a non-zero exit short-circuits the upload and the findings never reach Code Scanning.

Pin to a SHA

For supply-chain hygiene (and to satisfy alint’s own ci/github-actions@v1 bundled ruleset), pin the action to a commit SHA:

- uses: asamarts/alint@<40-char-sha>  # v0.9.20

Look up the SHA on the tag page.