# Pull request limits for CPython repo

**URL:** <https://discuss.python.org/t/pull-request-limits-for-cpython-repo/109564>\
**Category:** Core Development\
**Tags:** github, workflow\
**Created:** [October 20, 2026, 9:19am UTC](https://discuss.python.org/t/pull-request-limits-for-cpython-repo/109564 "2026-10-20T09:19:36Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![hugovk](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/hugovk/32/14505_2.png) [@hugovk](https://discuss.python.org/u/hugovk)\
**Post date:** [October 20, 2026, 9:19am UTC](https://discuss.python.org/t/pull-request-limits-for-cpython-repo/109564/1 "2026-10-20T09:19:37Z")

</div>

We’ve set a [limit for the maximum number of PRs](https://github.blog/changelog/2026-06-17-limit-open-pull-requests-for-users-without-write-access/) you can open at [python/cpython](https://github.com/python/cpython) to 3, [including drafts](https://github.blog/changelog/2026-10-08-draft-pull-requests-count-toward-pull-request-limits/).

- This _does not_ affect members of the core or triage teams.

- If you have more than 3 PRs already open, they stay open, but you won’t be able to open another before dropping below the limit.

We have done this following several recent incidents of bulk PR creation in a short amount of time, and we’re struggling to handle them. For example:

- Today: 21 CPython [PRs](https://github.com/python/cpython/pulls/limadog9) opened in a single two-hour burst across about 19 unrelated stdlib areas, as part of 177 template-written [PRs](https://github.com/pulls?q=is%3Apr+author%3Alimadog9) sent to 13 repos in three weeks. Account [banned](https://github.com/atuinsh/atuin/pull/4470) by one project.

- October: 19 CPython [PRs](https://github.com/python/cpython/pulls/esadomer) opened plus 13 companion [issues](https://github.com/python/cpython/issues/esadomer) in a 20-minute burst across about 22 unrelated stdlib modules.

- October: 7 CPython [issues](https://github.com/python/cpython/issues/sricursion) opened, then then 7 matching [PRs](https://github.com/python/cpython/pulls/sricursion) within a single minute across unrelated modules, all 14 still untouched by a reviewer, from an account with 60 [PRs](https://github.com/pulls?q=is%3Apr+author%3Asricursion) spread over 18 repos.

- September: 17 CPython [PRs](https://github.com/python/cpython/pulls/v0ropaev) opened over three days across unrelated modules, as part of 225 [PRs](https://github.com/pulls?q=is%3Apr+author%3Av0ropaev) across ~50 repos.

- September: A user whose profile boasts a “117 PRs merged upstream” badge, opened 6 CPython [PRs](https://github.com/python/cpython/pulls/sankalpsthakur) in two hours against unrelated modules, as part of 487 [PRs](https://github.com/pulls?q=is%3Apr+author%3Asankalpsthakur) across ~40 repos, about half of those closed unmerged since August.

Yes, these do look LLM generated, and no, we don’t want to be the first humans to read that code.

(We also get mass issue reports, but unfortunately GitHub has no configurable limit for this.)

A reminder from our [AI policy](https://devguide.python.org/getting-started/ai-tools/):

> Authors must review the work done by AI tooling in detail to ensure it actually makes sense before proposing it as a PR or filing it as an issue.
> 
> We expect PR authors and those filing issues to be able to explain their proposed changes in their own words.

And:

> Maintainers may close issues and PRs that are not useful or productive, without explanation, regardless of whether AI tools were used or not.
> 
> If a contributor repeatedly opens unproductive issues or PRs, they may be blocked from contributing to the project because it is disruptive and disrespectful of the maintainers time.

---

_[View the full topic](https://discuss.python.org/t/pull-request-limits-for-cpython-repo/109564)._
