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.
This was developed using https://github.com/jsoref/piskel/tree/spell-check, you can see the runs here: https://github.com/jsoref/piskel/actions/
Historically, I'd run a private spell checking tool against a repository and then just contribute the fixes. And then a couple of years later, I'd come back and repeat the process. To the extent that I manage to get back to a project, that works. But the alternative is actually offering a tool that projects can use to catch errors in advance. If you're interested, I'm happy to make a PR w/ the GitHub action.
I'm still getting used to using this as an Action, especially the idea of telling it to ignore CSS colors -- which resulted in a bit of a goose chase trying to figure out where
sper
andnvas
were coming from. In normal usage, when one tries to add a misspelling, the tool will annotate the new word and it's pretty obvious.