-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Fix mypy checks in CI to also run for scripts #60898
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
Fix mypy checks in CI to also run for scripts #60898
Conversation
Mypy Checks in CI have not been run on "scripts" folder - only on dev folder and if a mypy error creeped-in, it remained undetected unless someone run `pre-push` mypy check that instead of folders run it on individual files. This PR fixes the errors that creeped in and fixes the CI so that mypy-dev also checks scripts.
jscheffl
left a comment
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.
Ups, cool! Thanks for fixing!
Thanks to @mlauter for being inquisitive on slack :D |
Backport failed to create: v3-1-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker 7214ff8 v3-1-testThis should apply the commit to the v3-1-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
Mypy Checks in CI have not been run on "scripts" folder - only on dev folder and if a mypy error creeped-in, it remained undetected unless someone run `pre-push` mypy check that instead of folders run it on individual files. This PR fixes the errors that creeped in and fixes the CI so that mypy-dev also checks scripts. (cherry picked from commit 7214ff8) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
|
Backport in #60906 |
…60906) Mypy Checks in CI have not been run on "scripts" folder - only on dev folder and if a mypy error creeped-in, it remained undetected unless someone run `pre-push` mypy check that instead of folders run it on individual files. This PR fixes the errors that creeped in and fixes the CI so that mypy-dev also checks scripts. (cherry picked from commit 7214ff8)
Mypy Checks in CI have not been run on "scripts" folder - only on dev folder and if a mypy error creeped-in, it remained undetected unless someone run `pre-push` mypy check that instead of folders run it on individual files. This PR fixes the errors that creeped in and fixes the CI so that mypy-dev also checks scripts.
Mypy Checks in CI have not been run on "scripts" folder - only on dev folder and if a mypy error creeped-in, it remained undetected unless someone run `pre-push` mypy check that instead of folders run it on individual files. This PR fixes the errors that creeped in and fixes the CI so that mypy-dev also checks scripts.
Mypy Checks in CI have not been run on "scripts" folder - only on dev folder and if a mypy error creeped-in, it remained undetected unless someone run
pre-pushmypy check that instead of folders run it on individual files.This PR fixes the errors that creeped in and fixes the CI so that mypy-dev also checks scripts.
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.