-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run cspell
in CI
#2622
Run cspell
in CI
#2622
Conversation
1d2b532
to
138c439
Compare
Oh nice, that caught a bunch of stuff already! Do we have to check in that new |
I suppose not. Updated. |
c0e685f
to
80e397d
Compare
Updated to only install |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm slightly hesitant of making this a required part of CI. I agree that we should avoid typos and misspellings whenever possible, but I wonder if many PRs will end up being blocked on unknown terms and require regular updates to the cspell configuration.
I think there's no harm in trying this out, but if it becomes really annoying, then I will suggest removing the check.
I added a VS Code
cspell
configuration a while ago but it relies on people having the extension enabled, and noticing the things it detects. Instead, let's enforce this in CI. I've verified that the extension is still able to read the config.