Krzysztof kuhy Rudnicki a473e91485 Stop installing linters the pre-commit jobs never use, and add cache fallbacks ... Two follow-ups measured on the warm-cache run of d56b936, where the three pre-commit jobs were 39-44s split as: 4s runner setup, 9s pip, 2s cache restore, 23s hooks. The 9s pip was pure waste. Every linting hook runs in its own isolated env -- ruff, mypy, pylint, bandit and codespell each come from their own repo+rev, mypy and pylint declaring their own additional_dependencies -- and the only local hooks in the pre-commit stage need bash and python3. The pytest-coverage hook, the one thing that would need the real dependency set, is stages: [pre-push] and never runs here. Verified by running all three configs green in a venv containing pre-commit and nothing else. The pin is grepped out of requirements.txt so it cannot drift from the dependency-freshness gate. restore-keys is added because the exact key includes the config hash, so the next hook-rev bump -- this session did one -- would have been a total miss and reinstalled everything. A prefix hit rebuilds only the changed hook. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019kMvSMtsVMB3d2uoZ56pbp		2026-09-12 18:22:39 +02:00
..
workflows	Stop installing linters the pre-commit jobs never use, and add cache fallbacks	2026-09-12 18:22:39 +02:00