How to use codespell to test a project's incoming PRs via Continuous Integration (ex. TravisCI) about codespell HOT 10 CLOSED

Found https://blog.eleven-labs.com/en/how-to-check-the-spelling-of-your-docs-from-travis-ci/

from codespell.

We use it here:

https://github.com/mne-tools/mne-python/blob/master/.travis.yml#L173

And the Makefile (make codespell for interactive mode and make codespell-error for CI):

https://github.com/mne-tools/mne-python/blob/master/Makefile#L99

from codespell.

Cool! Perhaps we can flesh this out in to a guide on the wiki ?

from codespell.

@larsoner Looks like it's possible to notify submitter of the results using a github token. Does mne-tools/mne-python do this ?

curl -i -H "Authorization: token $GITHUB_TOKEN" \
    -H "Content-Type: application/json" \
    -X POST -d "{\"body\":\"$ASPELL_RESULTS\"}" \
    https://api.github.com/repos/eleven-labs/eleven-labs.github.io/issues/$TRAVIS_PULL_REQUEST/comments

from codespell.

No we don't bother, just let the red CI status lead them to check. But it sounds potentially useful.

from codespell.

Lets keep this is open while I study this, larsoner. Then I'll write a short tut on how to integrate it and add it to the README.

from codespell.

My progress: https://gist.github.com/luzpaz/76c7cbbb7edcb916f1ce69a14453478a

from codespell.

Here is how you tell codespell to run on all changed files in a submitted PR:

mapfile -t files < <(git diff --name-only $TRAVIS_COMMIT_RANGE); codespell -d -q 3 -S "$CODESPELL_SKIPS" -I ./whitelist.txt  "${files[@]}"

from codespell.

Closing as solved

from codespell.

Folks over at numpy have another solution: numpy/numpy#13694

from codespell.