-
Notifications
You must be signed in to change notification settings - Fork 30
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 mypy_primer
on pull requests
#27
Comments
Thanks, yeah, running more stuff in CI is a good idea, but I'm not sure what exactly. When adding or changing projects, the thing that is most valuable is the "full" output (you need the full output because e.g. if you misconfigure and there's zero output, the diff is also zero). But "full" output is very verbose across all 100 projects — maybe we need a primer for primer output :-) For what it's worth, I usually just test locally with |
#28 (comment) is a good example of needing to see the full output to know things are broken :-) |
I guess that it is a good idea to run priper, when the source code changes.
This might catch possible regressions in the future.
The text was updated successfully, but these errors were encountered: