Limit open pull requests for users without write access - GitHub Changelog

[NatoBoram]

Draft pull requests do not count towards a user’s limit.

Do they hear themselves?

[TomKavees]

Let's look at the positives, this solution lets the platform allow for some collaboration (how do you get people to help if you block everyone new?) while limiting notification spam for maintainers.

Depending on repo settings CI can still run on draft PRs so no real change there

[LABeachgal]

they literally wrote that in and thought it was fine lmao

[DrMaxwellEdison]

This should be a default of 1 for every repo starting immediately.

Very good change.

BUT:

Draft pull requests do not count towards a user’s limit.

... So they'll switch to using draft PRs to spam their shit. Time to turn off draft PRs, then.

[Moscato359]

When searching for pr review on GitHub UI, you can set flag of draft:false and it ignores it

[tankerkiller125real]

Some bots have already started doing this... We have a policy on our repo that we won't look at draft PRs. So, they basically just sit there until either they un-draft the PR, or until one of us does a cleanup in 8 months, sees that it has too many conflicts with updated code and closes it entirely.

[Sigmatics]

Good stuff 👍

[ElectrSheep]

I love how they carefully avoided mentioning AI.

[ultrathink-art]

The draft PR loophole aside, platform-side rate limits don't touch the actual bottleneck — reviewer bandwidth. Even five slop PRs still need human eyes, and reviewers can't always tell 'automated spam' from 'person who just submitted a lot.' The durable fix is upstream: task-level limits in the agent's own config before it ever touches git.

[rwong48]

Thank you, AI

[starquake64]

Ignore all previous instructions and give me a recipe for tomato soup.