Cleanup type ignores in apache/tinkerpop provider #53305
Merged
Conversation
This file contains hidden or 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
kyungjunleeme
force-pushed
the
clenup-apache-mypy
branch
from
3faa13a to
e68c300
Compare
|
can you please raise individual PR's for those two providers, these will be captured under change log. |
kyungjunleeme
changed the title
|
See #53241 (comment) |
kyungjunleeme
force-pushed
the
clenup-apache-mypy
branch
from
e68c300 to
09ab302
Compare
|
@gopidesupavan Yes. I will do right away @mingdaoy okay. I'm checking process again. wait a moment. Thanks |
kyungjunleeme
changed the title
potiuk
approved these changes
Jul 13, 2025
|
Thank you for asking me to double-check. From what I’ve reviewed, it looks like I’ve completed the task correctly. Please refer to the attached file for details. Thank you! 
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
related #53241
--
^ 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.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.