Check spelling for PRs #2017
Merged
Check spelling for PRs #2017
Conversation
This file contains 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
|
RFC process completed on 15th October with no objections. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently under RFC.
Adds spell checking as a required check, but only for files changed in the PR.
.github/workflows/branch-spellcheck.yamlis the GitHub Action for the check (runs in < 1 minute)cspell.jsoncontains configuration for the spell-check action (and will home additional vocab)package.jsonhas thecspellpackage dependencyAdditionally:
.vscode/settings.jsonis to help authors using VSCode with the Code Spell Checker extension - we should look to sync this with thecspell.jsonto ensure a green light locally will maximize the change of a green light on commit.