This is an automated email from the ASF dual-hosted git repository.

janhoy pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/solr.git


The following commit(s) were added to refs/heads/main by this push:
     new 78923482727 Cap concurrent open PRs from non-committers at 7 (#5163)
78923482727 is described below

commit 78923482727b8530d26ad08db734712ab2dacb12
Author: Jan Høydahl <[email protected]>
AuthorDate: Wed Oct 21 23:45:51 2026 +0200

    Cap concurrent open PRs from non-committers at 7 (#5163)
---
 .asf.yaml                       | 8 ++++++++
 .github/renovate.json           | 2 +-
 dev-docs/how-to-contribute.adoc | 1 +
 3 files changed, 10 insertions(+), 1 deletion(-)

diff --git a/.asf.yaml b/.asf.yaml
index 9037d8ca285..30e73f45152 100644
--- a/.asf.yaml
+++ b/.asf.yaml
@@ -18,6 +18,14 @@ github:
     merge:  false
     rebase: false
 
+  # Cap how many pull requests a contributor without write access may have 
open at once.
+  # See https://github.com/apache/infrastructure-asfyaml#pr_creation_cap
+  pull_requests:
+    creation_cap:
+      enabled: true
+      max_open_pull_requests: 7
+      include_drafts: true
+
   # TODO: Add to this list for each new minor release
   protected_branches:
     main: {}
diff --git a/.github/renovate.json b/.github/renovate.json
index b2b71b6ff81..8ed2c997d57 100644
--- a/.github/renovate.json
+++ b/.github/renovate.json
@@ -208,7 +208,7 @@
     }
   ],
   "schedule": ["before 9am on the first day of the month"],
-  "prConcurrentLimit": 300,
+  "prConcurrentLimit": 7,
   "prHourlyLimit": 20,
   "minimumReleaseAge": "5 days"
 }
diff --git a/dev-docs/how-to-contribute.adoc b/dev-docs/how-to-contribute.adoc
index 4ff6edeaae5..508825d82a6 100644
--- a/dev-docs/how-to-contribute.adoc
+++ b/dev-docs/how-to-contribute.adoc
@@ -40,6 +40,7 @@ In order to make a new contribution to Solr you will use the 
fork you have creat
 * The PR will run a gradle pre-commit task that will do some basic checks of 
your changes. This is run as a Github Action and the results can be viewed from 
your PR.
 * If you properly named your PR you will see it automatically linked to your 
Jira issue when you view the issue.
 * If your PR is still a work in progress, you can use the 
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests#draft-pull-requests[PR
 Draft feature] of Github to denote draft status.
+* Contributors without write access to the repository can have at most seven 
pull requests open at a time, drafts included. GitHub will refuse to create 
further PRs until one of your open ones is merged or closed. If you hit the 
limit, please help your earlier contributions over the line before starting 
something new. Committers are not subject to this limit.
 5. At this point, you will need a Solr committer to review your change and 
help to get it merged upstream. You can use the 
https://solr.apache.org/community.html[Solr Developers Mailing List] to get 
attention to your issue.
 
 ## PR Do-s and Don't-s

Reply via email to