alamb opened a new pull request, #11560: URL: https://github.com/apache/arrow-rs/pull/11560
# Which issue does this PR close? - N/A. Follows the model of [apache/datafusion#25973](https://github.com/apache/datafusion/pull/25973), which came out of [DataFusion discussion #24413](https://github.com/apache/datafusion/discussions/24413). # 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 in apache/datafusion#25973. # What changes are included in this PR? Enable `github.pull_requests.creation_cap` in `.asf.yaml` and set `max_open_pull_requests` to `3`, and add a "Creating Pull Requests" section to `CONTRIBUTING.md` describing the limit. The limit applies only to users without write access, and only counts open, non-draft PRs. References: - ASF support: [apache/infrastructure-asfyaml#111](https://github.com/apache/infrastructure-asfyaml/pull/111) - Airflow example: [apache/airflow#73758](https://github.com/apache/airflow/pull/73758) - DataFusion: [apache/datafusion#25973](https://github.com/apache/datafusion/pull/25973) Allowlist support via `.asf.yaml` is being added in [apache/infrastructure-asfyaml#135](https://github.com/apache/infrastructure-asfyaml/pull/135). Until then, a committer can manually close/reopen if a contributor has more than 3 mergeable PRs in flight. # 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. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
