Balancing Global Warning Enforcement vs. Silent CI Passes in ESLint

Question

The goal is to set a CI gate that blocks new warning‑level issues while preventing unnecessary merge rejections from existing warnings.

Using `--max-warnings=0` forces a non‑zero exit code on any warning, which is strict but requires a clean baseline before enabling; `--quiet` hides all warnings and keeps the exit code zero, allowing merges but masking emerging issues.

Because the CLI flags apply globally and cannot limit warnings to changed files, teams must decide whether to enforce strict gating after baseline cleanup or use silent mode together with external diff‑aware tooling, and whether native diff‑scoped warning handling exists.

Should the CI configuration adopt `--max-warnings=0` after baseline cleanup, or combine `--quiet` with external diff‑aware tooling? Is there a supported way to scope warning thresholds to changed files in ESLint 9, or must additional plugins be used?

Tasadduq Burney · Answer

Direct ResolutionThe CI configuration should adopt --max-warnings=0 only after a complete baseline cleanup of all existing warnings has been achieved. For preventing merge rejections based solely on *new* warnings, combining --max-warnings=0 with external, diff-aware tooling is the required pattern, as ESLint lacks native support for file-change scoping.Likely Explanation vs. Confirmed FactsThe desire to block new warnings without failing on old ones is a common CI challenge. The likely explanation is that ESLint's CLI flags are global; the confirmed fact is that ESLint 9 does not natively scope warning thresholds to changed files.Required StepsRun ESLint without strict flags to generate a full report of all current warnings.Address and fix all existing warnings across the codebase until the report shows zero warnings.Once the baseline is clean, configure the CI to run ESLint with --max-warnings=0.Integrate a pre-commit or CI step using external diff-aware tooling (e.g., comparing staged files against the last successful commit) to run ESLint only on changed files, ensuring --max-warnings=0 applies only to the delta.Missing Diagnostic DetailTo refine the recommendation, confirm the capability and tooling available in the current CI environment for generating file change lists (e.g., git diff --name-only output).

Balancing Global Warning Enforcement vs. Silent CI Passes in ESLint

1 answer

Direct Resolution

Likely Explanation vs. Confirmed Facts

Required Steps

Missing Diagnostic Detail

Your perspective belongs here.

1 question comment

Baseline Prerequisite