AI-Generated PR Spam Is the New Email Spam
A thread on AI-generated pull request spam landed with strong resonance. Maintainers described the problem as structurally identical to email spam in the early 2000s, where the volume is high, the quality is low, and the burden falls entirely on the recipient. One maintainer said they now require all new contributors to meet a maintainer in a non-textual format before merging a first PR. Another proposed redirecting token credits to open-source projects so maintainers could use AI tooling on their own terms.
The debate over solutions split quickly. Some wanted blanket bans on AI-generated issues and PRs. Others pointed out that an AI agent reviewing AI-generated slop is not the answer, it just adds latency to the same problem.
This is a real operational cost being imposed on volunteer maintainers, and it is growing. The signal across threads today is that AI-generated content at scale, whether blog posts, research papers, or PRs, is degrading the quality of shared infrastructure that the whole ecosystem depends on.
So what?
If you maintain open-source projects or accept external contributions, you need a policy now, not later. The non-textual-intro approach is creative but does not scale. The more interesting systemic question is whether open-source hosting platforms like GitHub will build spam filtering at the PR level, which is an open product problem worth solving.