mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-09 12:17:13 +00:00
kevinveenbirkenbachandClaude Opus 5
8d45159233
The runner sent both streams to /dev/null and then classified by exit code, so a failure produced one line -- "FAILED ansible-lint" -- with no code and no message. A lint finding, a crash and a lock conflict were indistinguishable, which is exactly the state a quality run left me in while ansible-lint was clean on the host at the same commit. Output now goes to a temp file, is discarded on success because ansible-lint is verbose when it passes, and is written to stderr together with the exit code when it fails. The accepted codes are untouched, so a passing run behaves exactly as before. run_ruff already reports this way, which is why the TID252 error it hit was fixable on sight. This changes no outcome. The failure that motivated it has not recurred, so the new path is still unexercised against a real fault. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Lint Scripts
This directory contains scripts that run repository lint checks.
- 🧹 Execute focused lint checks for workflows, Ansible, Python, and shell scripts
- 🔎 Keep lint entry points small, explicit, and callable from
make - ✅ Separate lint execution from tool installation and environment bootstrap
The scope of this folder is lint execution.
Tool installation belongs in scripts/install, while build and test workflows should stay in their dedicated script directories.