-
Notifications
You must be signed in to change notification settings - Fork 466
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
How to use codespell to test a project's incoming PRs via Continuous Integration (ex. TravisCI) #139
Comments
We use it here: https://github.com/mne-tools/mne-python/blob/master/.travis.yml#L173 And the Makefile ( https://github.com/mne-tools/mne-python/blob/master/Makefile#L99 |
Cool! Perhaps we can flesh this out in to a guide on the wiki ? |
@larsoner Looks like it's possible to notify submitter of the results using a github token. Does mne-tools/mne-python do this ?
|
No we don't bother, just let the red CI status lead them to check. But it sounds potentially useful. |
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. |
Here is how you tell codespell to run on all changed files in a submitted PR:
|
Closing as solved |
Folks over at numpy have another solution: numpy/numpy#13694 |
Has anyone seen or used codespell as a unit test that gets triggered in TravisCI when a new PR submitted ?
Downstream ticket: https://freecadweb.org/tracker/view.php?id=3205
The text was updated successfully, but these errors were encountered: