docs: limit concurrent open pull requests for contributors without write access

Ask contributors without write access to keep no more than three pull requests
open at the same time, so that maintainer review — the project's limiting
resource — is not spread too thin, enforced through the repository's pull
request limit. Contributors with write access, who are actively engaged with
the project, are not restricted; anyone with a genuine need to exceed the limit
can raise it with a maintainer.

Signed-off-by: Joshua Hoblitt <josh@hoblitt.com>
(cherry picked from commit 83b2c2e488)
This commit is contained in:
Joshua Hoblitt authored and Mergify committed 2026-08-06 19:55:07 +00:00
1 parent d31acaa26a
commit e28442b436
2 files changed
+10

No files matched your search

+3
View File
@@ -30,6 +30,9 @@ API, because those comments become the CRD descriptions.
* Sign off every commit with `git commit -s`. A bot enforces the DCO.
* Open pull requests against `master`, from a branch in a fork. Rebase onto upstream; never merge
upstream into a branch.
* If you do not have write access, keep no more than three pull requests open at once; the
repository enforces this. It does not apply to contributors with write access. Ask a maintainer
if you have a genuine need to exceed it.
* Opening a pull request non-interactively, such as by passing a body to `gh pr create`, skips the
template that GitHub would otherwise supply. Read
[the template](.github/PULL_REQUEST_TEMPLATE.md) and fill in its checklist regardless.
@@ -207,6 +207,13 @@ Before opening the PR:
* If there are code changes, add unit tests and verify that all unit tests are passing. See [Unit Tests](#unit-tests) below on running unit tests.
* Rebase on the latest upstream changes
### Limit concurrent pull requests
Contributors without write access should keep no more than three pull requests open at the same
time, so that maintainer review — the project's limiting resource — is not spread too thin. The
repository enforces this: with three open, merge or close one before opening the next. If you have a
genuine need to exceed it, raise it with a maintainer first.
### Regression Testing
All pull requests must pass all continuous integration (CI) tests before they can be merged. These tests