jactionlint for VS Code

Lints GitHub Actions workflows, composite actions and Dependabot files with the jactionlint CLI (must be on PATH, or set jactionlint.path).

• Findings in the Problems panel, with the rule ID linking to its documentation
• The repository is linted on startup, on save and when its files change on disk; unsaved edits are linted through stdin
• Quick fixes from jactionlint's own fixes, marked when they may change behavior
• "Ignore on this line" adds a # jactionlint ignore=<rule> comment
• "Fix all jactionlint findings in this file", also as source.fixAll.jactionlint for editor.codeActionsOnSave
• Commands to apply the safe fixes, or all fixes, across the workspace
• Status bar count of findings

"[yaml]": { "editor.codeActionsOnSave": { "source.fixAll.jactionlint": "explicit" } }

Settings

.github/jactionlint.yaml and the baseline apply as on the command line. jactionlint only checks inside a git repository; elsewhere the extension shows nothing.

Known limits: each workspace folder is linted as its own repository, and a buffer linted through stdin sees the saved versions of the other files.

Develop

bun install
bun run build            # bundles to out/extension.js
bun run test:unit        # bun tests
bun run test:integration # launches VS Code; needs jactionlint

Press F5 ("Run jactionlint") to launch an Extension Development Host on this repository, whose own workflows it lints. examples/ holds the workflow the integration tests use.