-
Notifications
You must be signed in to change notification settings - Fork 50
improve nightly workflow open issues for mypy #1242
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
Conversation
| mypy python | ||
| mypy python 2>&1 | tee mypy-output.log || true | ||
| - name: Create mypy failure issue |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can this be done for other types of failures too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We already do this for pytest failures. i think every other type of fialure we might have should never make it into main.
Also i'm going to test that this actually works on this PR so there may be some noise of opened issues
386a1dd to
d8696cf
Compare
No description provided.