Pull request limits are cutting down the noise

GitHub just dropped a new crowd-control tool for open-source projects: maintainers can now cap how many proposed code changes a stranger can have open at once. In plain English, if someone without special access keeps flooding a project with submissions, they’ll hit a limit and have to finish or close one before tossing in more. Drafts won’t count, trusted regulars can skip the line, and yes, AI-made submissions count too. The company says this is about saving volunteer maintainers from drowning as monthly submissions have exploded from 25 million to 90 million.

But the real show is in the comments, where the community instantly split into camps. Some people were basically standing on tables applauding. One commenter called it a "really solid move" and compared the dream setup to email: imagine if after sending too many ignored messages, you were simply cut off. "I would KILL for that," they joked, which is honestly the kind of dramatic energy this announcement summoned. Others were way more cynical, with one bluntly accusing GitHub of benefiting from the very chaos it now claims to fix: the noise is part of the business model, they argued.

Then came the spicy future-of-coding takes. One commenter suggested the next logical step is skipping outside code entirely: outsiders submit ideas and bug reports, while maintainers and large language models—AI writing tools—do the actual work. Another sneered that many so-called contributors are basically just "coding agents" with extra steps. In other words: GitHub says this is about reducing clutter, but the comment section turned it into a full-blown debate over spam, AI slop, and whether open source is becoming a gated club with better bouncers.