Vale alert level (MinAlertLevel) fails CI on warnings in CI
Vale classifies each alert as suggestion, warning, or error. The exit behavior depends on MinAlertLevel (and, in the action, fail_on_error / reviewdog level). If it is set too low, style suggestions fail the build instead of just annotating it.
What this error means
The docs job fails even though the summary shows "0 errors" but "12 warnings" or suggestions, because the alert threshold treats warnings as failing.
docs/intro.md
8:1 warning 'utilize' is wordy. Use 'use'. write-good.TooWordy
0 errors, 12 warnings and 3 suggestionsCommon causes
MinAlertLevel is set to suggestion or warning
A low MinAlertLevel in .vale.ini makes Vale surface (and, with strict gating, fail on) non-error alerts.
The action gates on the wrong level
A CI wrapper that fails on any reported alert will break the build on style suggestions you meant to be advisory.
How to fix it
Set MinAlertLevel to error for gating
Report at a lower level for humans but gate CI only on errors so warnings and suggestions do not fail the job.
MinAlertLevel = error
[*.md]
BasedOnStyles = Vale, write-goodDowngrade specific rules instead of the whole level
Keep gating on errors but soften a noisy rule to warning so it annotates without failing.
[*.md]
BasedOnStyles = write-good
write-good.TooWordy = warningHow to prevent it
- Gate CI on
MinAlertLevel = error; use warnings/suggestions for review only. - Tune individual rule severities rather than lowering the global threshold.
- Document which alert levels are advisory versus blocking for contributors.