ci(web): tighten ESLint --max-warnings to 1204 baseline (was 2000)
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
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>
This commit is contained in:
parent
dfc61e8408
commit
a514f4986b
1 changed files with 8 additions and 5 deletions
13
.github/workflows/ci.yml
vendored
13
.github/workflows/ci.yml
vendored
|
|
@ -124,11 +124,14 @@ jobs:
|
|||
working-directory: apps/web
|
||||
|
||||
- name: Lint
|
||||
# NOTE: --max-warnings is temporarily raised to 2000 while the
|
||||
# team resorbs the ESLint warning backlog (1167 at last count,
|
||||
# mostly @typescript-eslint/no-explicit-any and unused vars).
|
||||
# Lower this gradually as warnings are fixed.
|
||||
run: npx eslint --max-warnings=2000 .
|
||||
# ESLint warning baseline freeze (v1.0.10 polish):
|
||||
# 1204 is the current count of legacy warnings (mostly the
|
||||
# custom no-restricted-syntax 721, plus @typescript-eslint
|
||||
# no-non-null-assertion 139, no-unused-vars 134,
|
||||
# no-explicit-any 115, react-hooks/exhaustive-deps 47).
|
||||
# CI fails on ANY new warning. Lower this number as warnings
|
||||
# are resorbed by feature work; never raise it.
|
||||
run: npx eslint --max-warnings=1204 .
|
||||
working-directory: apps/web
|
||||
|
||||
- name: Typecheck
|
||||
|
|
|
|||
Loading…
Reference in a new issue