GitHub ponders kill switch for pull requests to stop AI slop
(2026/02/03)
- Reference: 1770150743
- News link: https://www.theregister.co.uk/2026/02/03/github_kill_switch_pull_requests_ai/
- Source link:
GitHub, the Microsoft code-hosting shop that popularized AI-assisted software development, is having some regrets about its Copilot infatuation.
Last week, product manager Camilla Moraes opened [1]a GitHub community discussion to address "a critical issue affecting the open source community: the increasing volume of low-quality contributions that is creating significant operational challenges for maintainers."
AI slop has come home to roost and GitHub wants help from its community of software developers to figure out how to manage the mess.
[2]
"We've been hearing from you that you're dedicating substantial time to reviewing contributions that do not meet project quality standards for a number of reasons – they fail to follow project guidelines, are frequently abandoned shortly after submission, and are often AI-generated," Moraes wrote.
[3]
[4]
"As AI continues to reshape software development workflows and the nature of open source collaboration, I want you to know that we are actively investigating this problem and developing both immediate and longer-term strategic solutions."
Moraes said GitHub is considering various options. These include possibly giving maintainers the option to disable pull requests entirely or to restrict pull requests to project collaborators; the ability to delete pull requests from the interface (to avoid having to look at AI slop); more granular permission settings for creating and reviewing pull requests; triage tools, possibly AI-based; and transparency/attribution mechanisms for signaling when AI tools are used.
[5]
GitHub did not immediately respond to a request to quantify the scope of the problem, which can show up in subpar pull requests (PRs) – code changes submitted to a Git repo in the hope they will be reviewed and merged into the codebase – and in shoddy bug reports (which may be accompanied by a pull request to fix the flaw).
But several [6]thread [7]participants acknowledged that dealing with AI-generated code and comments has become a pressing problem.
According to [8]Xavier Portilla Edo , head of cloud infrastructure at Voiceflow and a part of the [9]Genkit core team, only "1 out of 10 PRs created with AI is legitimate and meets the standards required to open that PR."
[10]
Other open source projects have been trying to deal with the tide of AI slop that has swelled over the past two years. [11]Daniel Stenberg , founder and lead developer of curl, and the [12]Python security developer Seth Larson have both been vocal in their objections to the maintenance burden created by low-quality AI-generated bug reports. Despite Stenberg's acknowledgement that [13]AI bug reports can be helpful if done properly, the curl project recently [14]shut down its bug bounty program to remove the incentive to submit low quality bug reports, whether authored by AI or otherwise.
[15]DIY AI bot farm OpenClaw is a security 'dumpster fire'
[16]Notepad++ update service hijacked in targeted state-linked attack
[17]Azure outages ripple across multiple dependent Microsoft services
[18]Firefox makes AI optional, like it probably should have been all along
Jiaxiao (Joe) Zhou, a software engineer on Microsoft's Azure Container Upstream team and maintainer of Containerd's Runwasi project and SpinKube, responded to Moraes about how AI code submissions are affecting open source maintainers.
"We held an internal session to talk about Copilot and there is a discussion on the topic where maintainers feel caught between today's required review rigor (line-by-line understanding for anything shipped) and a future where agentic / AI-generated code makes that model increasingly unsustainable," he [19]said .
Zhou summarized these concerns as follows:
Review trust model is broken: reviewers can no longer assume authors understand or wrote the code they submit.
AI-generated PRs can look structurally "fine" but be logically wrong, unsafe, or interact with systems the reviewer doesn't fully know.
Line-by-line review is still mandatory for shipped code, but does not scale with large AI-assisted or agentic PRs.
Maintainers are uncomfortable approving PRs they don't fully understand, yet AI makes it easy to submit large changes without deep understanding.
Increased cognitive load: reviewers must now evaluate both the code and whether the author understands it.
Review burden is higher than pre-AI, not lower.
As [20]noted by Nathan Brake, a machine learning engineer at Mozilla.ai, the open source community needs to figure out how to preserve community incentives to participate when AI is doing the coding work that traditionally earned recognition and the contributor is only writing up the issue description.
"[In my opinion,] much of open-source is really at risk because of this: we need to figure out a way to encourage knowledge sharing to keep alive what makes open source and GitHub so special: the community," he said, pointing to [21]a recent presentation at FOSDEM by Abby Cabunoc Mayes that addressed the issue.
Chad Wilson, primary maintainer for [22]GoCD , expects that AI agents unleashed as a result of [23]OpenClaw and Moltbook are going to make things worse.
In [24]a post to the thread on Tuesday, he said that he had already dealt with one pull request related to documentation and realized that it was "plausible nonsense" only after spending significant time reviewing it.
With regard to AI disclosure requirements that have been endorsed by others, he said the risk is that the open source social compact will break if there's no way to easily tell whether one is interacting with a human or an AI bot.
"I'm generally happy to help curious people in issues and guide them towards contributions/solutions in the spirit of social coding," he wrote. "But when there is no widespread lack of disclosure of LLM use and increasingly automated use – it basically turns people like myself into unknowing AI prompters. That's insane, and is leading to a huge erosion of social trust." ®
Get our [25]Tech Resources
[1] https://github.com/orgs/community/discussions/185387
[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aYJ-DD6bEVXH9gHcNHm9pwAAAo4&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aYJ-DD6bEVXH9gHcNHm9pwAAAo4&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aYJ-DD6bEVXH9gHcNHm9pwAAAo4&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aYJ-DD6bEVXH9gHcNHm9pwAAAo4&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[6] https://github.com/orgs/community/discussions/185387#discussioncomment-15657800
[7] https://github.com/orgs/community/discussions/185387#discussioncomment-15672105
[8] https://github.com/orgs/community/discussions/185387#discussioncomment-15631403
[9] https://github.com/firebase/genkit
[10] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aYJ-DD6bEVXH9gHcNHm9pwAAAo4&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[11] https://www.theregister.com/2024/01/04/aiassisted_bug_reports_make_developers/
[12] https://www.theregister.com/2024/12/10/ai_slop_bug_reports/
[13] https://www.theregister.com/2025/10/02/curl_project_swamped_with_ai/
[14] https://www.theregister.com/2026/01/21/curl_ends_bug_bounty/
[15] https://www.theregister.com/2026/02/03/openclaw_security_problems/
[16] https://www.theregister.com/2026/02/02/notepad_plusplus_intrusion/
[17] https://www.theregister.com/2026/02/03/azure_virtual_machine_outage/
[18] https://www.theregister.com/2026/02/03/firefox_ai_kill_switch/
[19] https://github.com/orgs/community/discussions/185387#discussioncomment-15632728
[20] https://github.com/orgs/community/discussions/185387#discussioncomment-15664831
[21] https://fosdem.org/2026/schedule/event/AJGB73-the_synthetic_senior_rethinking_free_software_mentorship_in_the_ai_era/
[22] https://www.gocd.org/
[23] https://www.theregister.com/2026/02/03/openclaw_security_problems/
[24] https://github.com/orgs/community/discussions/185387#discussioncomment-15685251
[25] https://whitepapers.theregister.com/
Last week, product manager Camilla Moraes opened [1]a GitHub community discussion to address "a critical issue affecting the open source community: the increasing volume of low-quality contributions that is creating significant operational challenges for maintainers."
AI slop has come home to roost and GitHub wants help from its community of software developers to figure out how to manage the mess.
[2]
"We've been hearing from you that you're dedicating substantial time to reviewing contributions that do not meet project quality standards for a number of reasons – they fail to follow project guidelines, are frequently abandoned shortly after submission, and are often AI-generated," Moraes wrote.
[3]
[4]
"As AI continues to reshape software development workflows and the nature of open source collaboration, I want you to know that we are actively investigating this problem and developing both immediate and longer-term strategic solutions."
Moraes said GitHub is considering various options. These include possibly giving maintainers the option to disable pull requests entirely or to restrict pull requests to project collaborators; the ability to delete pull requests from the interface (to avoid having to look at AI slop); more granular permission settings for creating and reviewing pull requests; triage tools, possibly AI-based; and transparency/attribution mechanisms for signaling when AI tools are used.
[5]
GitHub did not immediately respond to a request to quantify the scope of the problem, which can show up in subpar pull requests (PRs) – code changes submitted to a Git repo in the hope they will be reviewed and merged into the codebase – and in shoddy bug reports (which may be accompanied by a pull request to fix the flaw).
But several [6]thread [7]participants acknowledged that dealing with AI-generated code and comments has become a pressing problem.
According to [8]Xavier Portilla Edo , head of cloud infrastructure at Voiceflow and a part of the [9]Genkit core team, only "1 out of 10 PRs created with AI is legitimate and meets the standards required to open that PR."
[10]
Other open source projects have been trying to deal with the tide of AI slop that has swelled over the past two years. [11]Daniel Stenberg , founder and lead developer of curl, and the [12]Python security developer Seth Larson have both been vocal in their objections to the maintenance burden created by low-quality AI-generated bug reports. Despite Stenberg's acknowledgement that [13]AI bug reports can be helpful if done properly, the curl project recently [14]shut down its bug bounty program to remove the incentive to submit low quality bug reports, whether authored by AI or otherwise.
[15]DIY AI bot farm OpenClaw is a security 'dumpster fire'
[16]Notepad++ update service hijacked in targeted state-linked attack
[17]Azure outages ripple across multiple dependent Microsoft services
[18]Firefox makes AI optional, like it probably should have been all along
Jiaxiao (Joe) Zhou, a software engineer on Microsoft's Azure Container Upstream team and maintainer of Containerd's Runwasi project and SpinKube, responded to Moraes about how AI code submissions are affecting open source maintainers.
"We held an internal session to talk about Copilot and there is a discussion on the topic where maintainers feel caught between today's required review rigor (line-by-line understanding for anything shipped) and a future where agentic / AI-generated code makes that model increasingly unsustainable," he [19]said .
Zhou summarized these concerns as follows:
Review trust model is broken: reviewers can no longer assume authors understand or wrote the code they submit.
AI-generated PRs can look structurally "fine" but be logically wrong, unsafe, or interact with systems the reviewer doesn't fully know.
Line-by-line review is still mandatory for shipped code, but does not scale with large AI-assisted or agentic PRs.
Maintainers are uncomfortable approving PRs they don't fully understand, yet AI makes it easy to submit large changes without deep understanding.
Increased cognitive load: reviewers must now evaluate both the code and whether the author understands it.
Review burden is higher than pre-AI, not lower.
As [20]noted by Nathan Brake, a machine learning engineer at Mozilla.ai, the open source community needs to figure out how to preserve community incentives to participate when AI is doing the coding work that traditionally earned recognition and the contributor is only writing up the issue description.
"[In my opinion,] much of open-source is really at risk because of this: we need to figure out a way to encourage knowledge sharing to keep alive what makes open source and GitHub so special: the community," he said, pointing to [21]a recent presentation at FOSDEM by Abby Cabunoc Mayes that addressed the issue.
Chad Wilson, primary maintainer for [22]GoCD , expects that AI agents unleashed as a result of [23]OpenClaw and Moltbook are going to make things worse.
In [24]a post to the thread on Tuesday, he said that he had already dealt with one pull request related to documentation and realized that it was "plausible nonsense" only after spending significant time reviewing it.
With regard to AI disclosure requirements that have been endorsed by others, he said the risk is that the open source social compact will break if there's no way to easily tell whether one is interacting with a human or an AI bot.
"I'm generally happy to help curious people in issues and guide them towards contributions/solutions in the spirit of social coding," he wrote. "But when there is no widespread lack of disclosure of LLM use and increasingly automated use – it basically turns people like myself into unknowing AI prompters. That's insane, and is leading to a huge erosion of social trust." ®
Get our [25]Tech Resources
[1] https://github.com/orgs/community/discussions/185387
[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aYJ-DD6bEVXH9gHcNHm9pwAAAo4&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aYJ-DD6bEVXH9gHcNHm9pwAAAo4&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aYJ-DD6bEVXH9gHcNHm9pwAAAo4&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aYJ-DD6bEVXH9gHcNHm9pwAAAo4&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[6] https://github.com/orgs/community/discussions/185387#discussioncomment-15657800
[7] https://github.com/orgs/community/discussions/185387#discussioncomment-15672105
[8] https://github.com/orgs/community/discussions/185387#discussioncomment-15631403
[9] https://github.com/firebase/genkit
[10] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aYJ-DD6bEVXH9gHcNHm9pwAAAo4&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[11] https://www.theregister.com/2024/01/04/aiassisted_bug_reports_make_developers/
[12] https://www.theregister.com/2024/12/10/ai_slop_bug_reports/
[13] https://www.theregister.com/2025/10/02/curl_project_swamped_with_ai/
[14] https://www.theregister.com/2026/01/21/curl_ends_bug_bounty/
[15] https://www.theregister.com/2026/02/03/openclaw_security_problems/
[16] https://www.theregister.com/2026/02/02/notepad_plusplus_intrusion/
[17] https://www.theregister.com/2026/02/03/azure_virtual_machine_outage/
[18] https://www.theregister.com/2026/02/03/firefox_ai_kill_switch/
[19] https://github.com/orgs/community/discussions/185387#discussioncomment-15632728
[20] https://github.com/orgs/community/discussions/185387#discussioncomment-15664831
[21] https://fosdem.org/2026/schedule/event/AJGB73-the_synthetic_senior_rethinking_free_software_mentorship_in_the_ai_era/
[22] https://www.gocd.org/
[23] https://www.theregister.com/2026/02/03/openclaw_security_problems/
[24] https://github.com/orgs/community/discussions/185387#discussioncomment-15685251
[25] https://whitepapers.theregister.com/
Excused Boots
"GitHub ponders kill switch for pull requests to stop AI slop"
Yes just fucking do it before you are become overwhelmed with slop and it all becomes irrelevant.
No; hang on you are owned by Sat Nad, who is (desperately) all in on this stuff so you really can’t can you?
Sorry, you’re doomed, get out now while you still can!
AI Slop Jockeys versus reality
thames
On the one hand we have the AI slop jockeys telling us that this this very thing is successfully used in proprietary code bases where we can't see the results.
On the other hand, when the evidence is openly and transparently visible, 90% of what AI does fails to meet even minimal standards and people are asking for ways to stop being inundated with AI slop.
Something is not adding up, and I suspect it's the people who are doing things behind closed doors who are the ones who have something to hide.
no option for no-PR
_wojtek
it's absurd that PR section is the only one that can't be disabled in project configuration right now...
"the increasing volume of low-quality contributions that is creating significant operational challenges for maintainers."
That explains much about Windows 11.