a514f4986b
Some checks are pending
Veza CI / Backend (Go) (push) Waiting to run
Veza CI / Frontend (Web) (push) Waiting to run
Veza CI / Rust (Stream Server) (push) Waiting to run
Veza CI / Notify on failure (push) Blocked by required conditions
E2E Playwright / e2e (full) (push) Waiting to run
Security Scan / Secret Scanning (gitleaks) (push) Waiting to run
The CI lint step was running with `--max-warnings=2000`, which left ~800 warnings of headroom — meaning every PR could quietly add new warnings without anyone noticing. The "raise gradually" intent in the comment never converted to action. Locked the gate at the current count (1204) so the dette stops growing. Top contributors : - 721 no-restricted-syntax (custom rule, mostly unicode/i18n) - 139 @typescript-eslint/no-non-null-assertion (the `!` operator) - 134 @typescript-eslint/no-unused-vars - 115 @typescript-eslint/no-explicit-any - 47 react-hooks/exhaustive-deps - 25 react-refresh/only-export-components - 23 storybook/no-redundant-story-name Operational rule: lower this number as warnings are resorbed by feature work — never raise it. New code must not add warnings; if you genuinely need an exception, add `// eslint-disable-next-line <rule> -- <reason>` rather than bumping the cap. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| ci.yml | ||
| e2e.yml | ||
| go-fuzz.yml | ||
| loadtest.yml | ||
| security-scan.yml | ||
| trivy-fs.yml | ||