You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@arrow.apache.org by gi...@apache.org on 2026/10/15 10:39:42 UTC
(arrow-rs) branch gh-readonly-queue/main/pr-11560-a743994d6cd5a7dc94c6f3609c7211576d205f61 created (now 6fbb45f1ac)
This is an automated email from the ASF dual-hosted git repository.
github-merge-queue[bot] pushed a change to branch gh-readonly-queue/main/pr-11560-a743994d6cd5a7dc94c6f3609c7211576d205f61
in repository https://gitbox.apache.org/repos/asf/arrow-rs.git
at 6fbb45f1ac chore: Limit open, non draft PRs to 3 for users without write access (#11560)
This branch includes the following new commits:
new 6fbb45f1ac chore: Limit open, non draft PRs to 3 for users without write access (#11560)
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
(arrow-rs) 01/01: chore: Limit open, non draft PRs to 3 for users without write access (#11560)
Posted by gi...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
github-merge-queue[bot] pushed a commit to branch gh-readonly-queue/main/pr-11560-a743994d6cd5a7dc94c6f3609c7211576d205f61
in repository https://gitbox.apache.org/repos/asf/arrow-rs.git
commit 6fbb45f1ac89cc4744fe1eda23ffb07abe401e20
Author: Andrew Lamb <an...@nerdnetworks.org>
AuthorDate: Thu Oct 15 10:39:19 2026 +0000
chore: Limit open, non draft PRs to 3 for users without write access (#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
https://github.com/apache/datafusion/discussions/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 <no...@anthropic.com>
Co-authored-by: Ed Seidl <et...@users.noreply.github.com>
---
.asf.yaml | 8 ++++++++
CONTRIBUTING.md | 11 +++++++++++
2 files changed, 19 insertions(+)
diff --git a/.asf.yaml b/.asf.yaml
index 910b13f909..40e91fbff6 100644
--- a/.asf.yaml
+++ b/.asf.yaml
@@ -82,6 +82,14 @@ github:
# enable updating head branches of pull requests
allow_update_branch: true
allow_auto_merge: true
+ # Limit open pull requests per user without write access.
+ #
+ # The number of open PRs far exceeds our review capacity. We limit non
+ # committers to 3 open, non draft PRs, to help us curate and focus on a
+ # smaller number of higher quality PRs.
+ creation_cap:
+ enabled: true
+ max_open_pull_requests: 3
# publishes the content of the `asf-site` branch to
# https://arrow.apache.org/rust/
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 34fc582af2..581498be23 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -62,6 +62,17 @@ ideas with the community to get feedback on implementation.
[good-first-issue]: https://github.com/apache/arrow-rs/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22
+## Creating Pull Requests
+
+With coding agents, the number of open PRs now far exceeds our review capacity.
+To encourage submitters to curate and prepare a small number of high quality PRs,
+and to help reviewers focus on them, users without write access are limited to
+**3 open, non-draft PRs** at a time.
+
+When possible, we recommend splitting your contributions into multiple smaller
+focused PRs rather than large PRs, because they are more likely to be reviewed
+quickly and are easier to understand and review.
+
## Developer's guide to Arrow Rust
### Setting Up Your Build Environment