April 21, 2026
AI ate your pull request
I don't want your PRs anymore
Open‑source maintainer says “no thanks” to your fixes — AI will handle it
TLDR: A maintainer says “no more pull requests,” preferring AI tools to write changes that match his style and avoid review headaches. Commenters split: some say fine, they’ll fork and re‑implement with AI; others suggest “prompt diffs,” while a few question if this really saves time—signaling a shift in how open source collaborates.
Cue the open‑source soap opera: a popular maintainer just told fans, “please stop sending pull requests,” the online way people ask to merge their code into a project. In a viral post, he says it’s faster and safer to use AI coding tools (large language models) that already know his style, avoid strangers’ risky changes, and skip the time‑zones-and-back‑and‑forth drama. His take: writing code isn’t the bottleneck anymore — understanding, design, and review are — so outside code doesn’t help much.
The comments lit up. One pragmatic voice, lou1306, says most style fights could be avoided with a simple rule: pass the style checks and don’t add extra add‑ons. Meanwhile, the spicy crowd brought heat. Jerkstate basically shrugged and said the quiet part loud: if you don’t want my code, I’ll just fork it and re‑implement — it’s nearly free now with AI. Others were zen about it: eschneider called the policy “fine,” adding that fixing your own bug and offering it back is a courtesy, not a right.
Then came the memes. Porphyra pitched a future where people submit “prompt diffs” — little AI instructions — so the maintainer can paste them into their bot and generate the change themselves. Gavmor poked the bear with a deadpan “Delaying what?”, questioning whether the review “round‑trip” is really the problem. The vibe: PRs are canceled, AI is the new co‑worker, and the community is split between “respect the maintainer’s workflow” and “cool, I’ll ship my own version.”
Key Points
- •The maintainer will not merge external pull requests due to security risk, style misalignment, and coordination overhead.
- •LLMs now generate code aligned with the maintainer’s preferences, reducing the value of external PRs.
- •The maintainer’s bottlenecks are understanding, designing, and reviewing—not writing code.
- •Contributors are encouraged to help by discussing ideas, filing detailed bug reports, and investigating issues.
- •Prototype code and shared prompts are welcome as references, even if the maintainer reproduces changes themselves.