Remove the Vale prose-linting check - #1890
Merged
Merged
Conversation
Vale (Google style guide rules) comments on nearly every docs PR -- dozens of passive-voice and contraction nits per PR, enough that the action rate-limits itself posting them. It is fail_on_error: false, so it never blocks anything; it just buries real review comments in noise. Spelling (cspell), formatting (prettier), markdown lint, and the link checker all stay. Removes the workflow, the .vale config and styles, and the package.json scripts. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Link check results: |
|
pmckinney-codat
enabled auto-merge
September 16, 2026 13:57
rodages
approved these changes
Sep 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Removes the Vale prose-linting check: the workflow (
check-vale.yml), the.vale.iniconfig and.vale/styles, and the threevale*scripts inpackage.json.Why
Vale runs the Google style guide against every docs PR and comments on nearly every changed line — passive voice, contractions, parentheses — to the point that the action rate-limits itself posting them (see the ~40 bot threads it left on #1889). It's configured with
fail_on_error: false, so it never actually blocks a PR; it just buries real review comments in noise. Overkill for the value it adds.Still in place: spell check (cspell), formatting (prettier), markdown lint, and the link checker.
Note for reviewer
"Vale linting" shows as a passing check on PRs today — worth confirming it isn't in the branch-protection required checks list before merging, so docs PRs don't wait on a check that never reports.
🤖 Generated with Claude Code