What exactly is the "remix model" Huntley proposes?

Huntley proposes that authors publish source code under an as-is license and that users make desired changes as small overlays, reused across development environments, Docker images, tests, CI, and agent sandboxes. The guiding principle is "Ideas over patches": maintainers have no obligation to review, merge, or maintain changes.

Has Huntley actually disabled pull requests on all his repositories?

As of writing, it could not be confirmed that he had actually disabled pull requests across all of his repositories. The piece describes his declaration as a proposal.

What is the concrete example Huntley gives for how remixing works?

He describes a user who wants to ban Git force push, which overwrites history. Instead of sending a pull request upstream, the user writes an overlay that patches Git, defined in one place and appearing consistently in the development environment, container image, and system tests — with an implementation example published in Nix.

AI Coding AssistantsOpen-Source AIITmedia AI＋15h agoNov 5, 2026, 06:01 JST

Geoffrey Huntley ends pull requests on GitHub, offers remix guides

Send on LINE

3 Key Points

What happened
Geoffrey Huntley said on October 14, 2026 that future code he publishes on GitHub will not accept pull requests, replaced by maintained guides on how to modify it.
Why it matters
The move signals a shift from sending changes upstream to having each user customize code locally, a third path between closed development and open contribution, with the cost falling on whoever maintains the customized version.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Get these free every morning

Context & Analysis

Huntley frames his proposal as a return to what open-source licenses already allow: modification without creating a claim on someone else's future time. He traces the problem back to Eric Raymond's 1997 essay "The Cathedral and the Bazaar," which contrasted closed, planned development with open, self-organizing contribution. GitHub turned the bazaar idea into a workflow where anyone could contribute via pull request. But Huntley argues the bazaar was already straining before AI wrote code, because it created an expectation that whoever publishes code owes maintenance without reward, while users became consumers demanding merges.

The declaration did not arrive in a vacuum. Through 2026, prominent open-source projects have been restricting outside contributions: curl's Daniel Stenberg ended a six-year bug bounty effective February 1, 2026, after AI-generated reports reached 20% of submissions in 2025 while the share of valid reports fell to 5%; tldraw's Steve Ruiz moved to auto-close all external pull requests; Ghostty's Mitchell Hashimoto limited external contributions of AI-generated code; and GitHub reportedly added a repository setting to disable pull requests in February 2026. RedMonk analyst called the situation "AI Slopageddon." Huntley's proposal can be read as offering a different entrance after maintainers had already begun closing the door.

The trade-offs are concrete. Pull requests have also served as quality control through third-party review, as a single point where security fixes are collected so all users are protected by one update, and as a record of why a change was needed. Under remixing, each change is its own responsibility and fixes scatter. The implementation example relies on Nix, which is known for a steep learning curve — Huntley himself has written that Nix is a terrible programming language — so the claim that agents have removed the knowledge barrier may hold for those who can use agents well, not for every user.

FAQ

What exactly is the "remix model" Huntley proposes?: Huntley proposes that authors publish source code under an as-is license and that users make desired changes as small overlays, reused across development environments, Docker images, tests, CI, and agent sandboxes. The guiding principle is "Ideas over patches": maintainers have no obligation to review, merge, or maintain changes.
Has Huntley actually disabled pull requests on all his repositories?: As of writing, it could not be confirmed that he had actually disabled pull requests across all of his repositories. The piece describes his declaration as a proposal.
What is the concrete example Huntley gives for how remixing works?: He describes a user who wants to ban Git force push, which overwrites history. Instead of sending a pull request upstream, the user writes an overlay that patches Git, defined in one place and appearing consistently in the development environment, container image, and system tests — with an implementation example published in Nix.

ITmedia AI＋Read Original Article

Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Get it free

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.