Skip to content

Conversation

@rich7420
Copy link
Contributor

related: #59402


^ 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 airflow-core/newsfragments.

@boring-cyborg boring-cyborg bot added area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch labels Dec 15, 2025
@rich7420
Copy link
Contributor Author

@Prab-27 this pr passed step 5.

@potiuk
Copy link
Member

potiuk commented Dec 16, 2025

Conflicts. I recommend others who make similar PRs to close the individual ones and make a "coarse grained" PRs with mulitple files fixed per PR. This will be far more efficient and require far less overhead from maintainers and cause far less noise and conflict resolution.

@rich7420
Copy link
Contributor Author

rich7420 commented Dec 17, 2025

@potiuk agree

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants