[Feature Request] Suggested way of automating this with CI jobs

[joohoi]

Is there a suggested way of running this as a static part of the workflow with Travis-CI for example? I feel that a hard fail would probably be too error prone, but something that would easily note that there might be spelling issues in the state of repo.

I really like how https://coveralls.io API can report back to GitHub issues, but I do acknowledge that this would mean running an static instance outside of Travis to handle the reporting.

Sorry for kind of open ended issue and rambling.

[jsoref]

I've written: https://github.com/checkstyle/checkstyle/blob/master/.ci/test-spelling-unknown-words.sh which interacts with Travis.

[jsoref]

A GitHub App/check/probot thing is definitely intriguing. I'm thinking about it a bit, but I haven't gone very far w/ it...

[henryiii]

A GitHub Action would be very interesting. See pre-commit's GHA, for example.

Edit: Actually, a pre-commit plugin or example would be great, see https://pre-commit.com. Then it would just take advantage of the existing pre-commit GHA and local usage, too.

[jsoref]

I've actually started working on this... It will eventually be in this repository.
For the time being, you can see the Action here:
https://github.com/jsoref/spelling-action
And a consumer here:
https://github.com/jsoref/test-test
With a sample runs:
https://github.com/jsoref/test-test/actions/runs/37887629

[jsoref]

@henryiii: this year I've released a number of alpha releases of check-spelling

As for a pre-commit hook, I'm actually getting close to being able to do that... Although It isn't a direct goal.

A pre-release version of the action supports nektos/act, so one could use that.

But something more lightweight could be implemented using the toolchain I'm using to clean up repositories before submitting PRs...

I think I'll probably close this once my action is closer to a 1.0 release, or at least when I stop calling it "alpha".