-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
Brings back mypy-checks #38597
Merged
Merged
Brings back mypy-checks #38597
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
potiuk
added
the
full tests needed
We need to run full set of tests for this PR to merge
label
Mar 28, 2024
Taragolis
approved these changes
Mar 28, 2024
potiuk
force-pushed
the
bring-back-mypy-checks
branch
2 times, most recently
from
March 28, 2024 22:12
c2c1cd6
to
dbcb0ef
Compare
hussein-awala
approved these changes
Mar 28, 2024
It was literally day-and-a-half or so, so I hope there won't be many things to fix 😁 |
Just one small issue :) |
During the last week refactor input on mypy checks was moved to another workflow and mypy checks were not running for a day. This change brings it back.
potiuk
force-pushed
the
bring-back-mypy-checks
branch
from
March 28, 2024 22:40
dbcb0ef
to
00ccd31
Compare
Should be fixed now. |
ephraimbuddy
added
the
changelog:skip
Changes that should be skipped from the changelog (CI, tests, etc..)
label
Mar 31, 2024
ephraimbuddy
pushed a commit
that referenced
this pull request
Mar 31, 2024
During the last week refactor input on mypy checks was moved to another workflow and mypy checks were not running for a day. This change brings it back. (cherry picked from commit a2f5307)
ephraimbuddy
pushed a commit
that referenced
this pull request
Mar 31, 2024
During the last week refactor input on mypy checks was moved to another workflow and mypy checks were not running for a day. This change brings it back. (cherry picked from commit a2f5307)
mathiaHT
pushed a commit
to mathiaHT/airflow
that referenced
this pull request
Apr 4, 2024
During the last week refactor input on mypy checks was moved to another workflow and mypy checks were not running for a day. This change brings it back.
utkarsharma2
pushed a commit
to astronomer/airflow
that referenced
this pull request
Apr 22, 2024
During the last week refactor input on mypy checks was moved to another workflow and mypy checks were not running for a day. This change brings it back.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area:dev-tools
changelog:skip
Changes that should be skipped from the changelog (CI, tests, etc..)
full tests needed
We need to run full set of tests for this PR to merge
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During the last week refactor input on mypy checks was moved to another workflow and mypy checks were not running for a day.
This change brings it back.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.