ci: Enforce PR limit to 3 for non-committers by 2010YOUY01 · Pull Request #25973 · apache/datafusion

2010YOUY01 · 2026-10-02T13:33:54Z

Which issue does this PR close?

Rationale for this change

See discussion for the rationale, most people are voting for 'set limit to 3' from the discussion.

What changes are included in this PR?

Enable github.pull_requests.creation_cap in .asf.yaml and set max_open_pull_requests to 3.

ASF support: apache/infrastructure-asfyaml#111.
Airflow example followed by this change: apache/airflow#73758.

Whitelist support through .asf.yaml is being added in apache/infrastructure-asfyaml#135, which is still open. Before that I think it's possible to do some manual close/reopen, if some contributor have > 3 concurrent PRs that is mergeable.

What is the testing strategy for this PR?

Should work since it's following the pattern in other ASF project above

I don't know if it's possible to test before merging

Are there any user-facing changes?

NA

codecov-commenter · 2026-10-02T14:01:25Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.62%. Comparing base (348553b) to head (daf5402).
⚠️ Report is 9 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #25973      +/-   ##
==========================================
+ Coverage   82.61%   82.62%   +0.01%     
==========================================
  Files        1145     1147       +2     
  Lines      444325   445128     +803     
  Branches   444325   445128     +803     
==========================================
+ Hits       367066   367774     +708     
- Misses      54972    55020      +48     
- Partials    22287    22334      +47

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

asolimando

Makes sense :)

alamb

Thank you -- this will be super helpful

nuno-faria · 2026-10-02T19:42:49Z

Should there be a note about this at https://datafusion.apache.org/contributor-guide/index.html?

alamb · 2026-10-02T19:47:37Z

Should there be a note about this at https://datafusion.apache.org/contributor-guide/index.html?

Yes. Great call. Specifically I think we should explain we are trying to help focus reviewer time / efforts (and the fewer open pRs by one contributor the more likely we will have time to review them)

I am also working on polishing up improving the guidelines here:

Update contributor guidelines regarding AI spam, reviews, code #24510

alamb · 2026-10-02T19:48:25Z

    allow_auto_merge: true
    # auto-delete head branches after being merged
    del_branch_on_merge: true
+    # Limit open pull requests per user without write access.


can we also explain the rationale here?
Something like "To try and more evenly spread the reviewer bandwidth around" or something like that?

It's a great explaination, updated.

Rich-T-kid

sounds like a good idea to me! What happens to existing PR's that exceed the 3 pr limit for non asf contributer? do they get closed automatically?

2010YOUY01 · 2026-10-03T01:05:03Z

Should there be a note about this at https://datafusion.apache.org/contributor-guide/index.html?

I agree, added.

sounds like a good idea to me! What happens to existing PR's that exceed the 3 pr limit for non asf contributer? do they get closed automatically?

No, but they can't open new PRs. The current solution is to close/reopen manually to prioritize PRs.

2010YOUY01 · 2026-10-04T01:26:51Z

Thank you all for the review. Let's merge it get it tested.

alamb · 2026-10-05T20:09:36Z

Thanks!

## Which issue does this PR close? Follows [DataFusion discussion apache#24413](apache#24413). ## Rationale for this change See discussion for the rationale, most people are voting for 'set limit to 3' from the discussion. ## What changes are included in this PR? Enable `github.pull_requests.creation_cap` in `.asf.yaml` and set `max_open_pull_requests` to `3`. - ASF support: [apache/infrastructure-asfyaml#111](apache/infrastructure-asfyaml#111). - Airflow example followed by this change: [apache/airflow#73758](apache/airflow#73758). Whitelist support through `.asf.yaml` is being added in [apache/infrastructure-asfyaml#135](apache/infrastructure-asfyaml#135), which is still open. Before that I think it's possible to do some manual close/reopen, if some contributor have > 3 concurrent PRs that is mergeable. ## What is the testing strategy for this PR? Should work since it's following the pattern in other ASF project above I don't know if it's possible to test before merging ## Are there any user-facing changes? NA

…pache#11560) # Which issue does this PR close? - N/A. # Rationale for this change With coding agents, the number of open PRs now far exceeds our review capacity. The goal of this change is to encourage submitters to help us curate and prepare a small number of high quality PRs, rather than opening many at once, and to help reviewers figure out where to focus their limited time. DataFusion recently adopted the same limit after discussion apache/datafusion#24413 - apache/datafusion#25973. # What changes are included in this PR? 1. Limit users without write access (non committers), to 3 open, non-draft PRs. # Are these changes tested? No. This is configuration consumed by ASF Infra and follows the pattern already in use in DataFusion and Airflow. It is not possible to test before merging. # Are there any significant user-facing changes? No code changes. Contributors without write access will be limited to 3 open, non-draft PRs at a time. --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com> Co-authored-by: Ed Seidl <etseidl@users.noreply.github.com>

ci: Enforce PR limit to 3 for non-committers

39c754a

github-actions Bot added the development-process Related to development process of DataFusion label Oct 2, 2026

asolimando approved these changes Oct 2, 2026

View reviewed changes

alamb approved these changes Oct 2, 2026

View reviewed changes

Rich-T-kid approved these changes Oct 2, 2026

View reviewed changes

review: comment, and contributor guide

daf5402

github-actions Bot added the documentation Improvements or additions to documentation label Oct 3, 2026

zhuqi-lucas approved these changes Oct 3, 2026

View reviewed changes

2010YOUY01 added this pull request to the merge queue Oct 4, 2026

Merged via the queue into apache:main with commit 6047791 Oct 4, 2026
43 checks passed

2010YOUY01 deleted the pr-limit branch October 4, 2026 01:36

github-actions Bot added the v56.0.0 label Oct 4, 2026

alamb mentioned this pull request Oct 14, 2026

chore: Limit open, non draft PRs to 3 for users without write access apache/arrow-rs#11560

Merged

mbutrovich mentioned this pull request Oct 15, 2026

ci: Limit open, non-draft PRs to 3 for users without write access apache/iceberg-rust#3465

Merged

This was referenced Oct 20, 2026

Discuss limiting open PRs per contributor without write access apache/datafusion-comet#7133

Closed

chore: limit open PRs for users without write access to 3 apache/datafusion-comet#7135

Merged

Navigation Menu

Repository navigation

ci: Enforce PR limit to 3 for non-committers - #25973

ci: Enforce PR limit to 3 for non-committers#25973
2010YOUY01 merged 2 commits into
apache:mainfrom
2010YOUY01:pr-limit

2010YOUY01 commented Oct 2, 2026

Uh oh!

codecov-commenter commented Oct 2, 2026 •

edited

Loading

Uh oh!

asolimando left a comment

Uh oh!

alamb left a comment

Uh oh!

nuno-faria commented Oct 2, 2026

Uh oh!

alamb commented Oct 2, 2026

Uh oh!

alamb Oct 2, 2026

Uh oh!

2010YOUY01 Oct 3, 2026

Uh oh!

Rich-T-kid left a comment

Uh oh!

2010YOUY01 commented Oct 3, 2026

Uh oh!

2010YOUY01 commented Oct 4, 2026

Uh oh!

Uh oh!

alamb commented Oct 5, 2026

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

Conversation

2010YOUY01 commented Oct 2, 2026

Which issue does this PR close?

Rationale for this change

What changes are included in this PR?

What is the testing strategy for this PR?

Are there any user-facing changes?

Uh oh!

codecov-commenter commented Oct 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

asolimando left a comment

Choose a reason for hiding this comment

Uh oh!

alamb left a comment

Choose a reason for hiding this comment

Uh oh!

nuno-faria commented Oct 2, 2026

Uh oh!

alamb commented Oct 2, 2026

Uh oh!

alamb Oct 2, 2026

Choose a reason for hiding this comment

Uh oh!

2010YOUY01 Oct 3, 2026

Choose a reason for hiding this comment

Uh oh!

Rich-T-kid left a comment

Choose a reason for hiding this comment

Uh oh!

2010YOUY01 commented Oct 3, 2026

Uh oh!

2010YOUY01 commented Oct 4, 2026

Uh oh!

Uh oh!

alamb commented Oct 5, 2026

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

codecov-commenter commented Oct 2, 2026 •

edited

Loading