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
@potiuk
Copy link
Member

potiuk commented Dec 16, 2025

I think - similarly to what I explained to @choo121600 -> file-by-file here is quite a bit too fine-grained, it causes conflicts and creates a lot of overhead for merging and running tests, it would be better to group those in a group of related files at the very least.

@choo121600
Copy link
Member

If even one of the related changes is merged first, it will cause conflicts in all the remaining other PR.
Therefore, it seems best for each person to group their own PRs into a single combined PR like this (#59501), and then merge those combined PRs one by one.

@choo121600
Copy link
Member

Otherwise, we would need to resolve conflicts in every PR each time one gets merged.

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.

3 participants