May 1, 2026
Pull request? More like pull drama
If I could make my own GitHub
Dev dreams of replacing GitHub — commenters instantly turn it into a tech cage match
TLDR: A developer imagined a cleaner, saner replacement for GitHub, saying today’s code-hosting sites are overloaded and awkward. Commenters turned it into a brawl: some mocked the ideas as emotional hand-holding, others said alternatives already exist, and many agreed people are hungry for something simpler.
A programmer posted a fantasy redesign of GitHub, the hugely popular website where people store code and review each other’s work, arguing the whole experience has become bloated, frustrating, and weirdly backwards. His big pitch? Stop letting people smash the “upload” button first and only find out afterward that everything is broken. He also wants code review to be less of a harsh yes/no marriage proposal and more like real life: messy, hesitant, and full of “fine, we’ll deal with it later.”
But the real fireworks were in the comments, where the community immediately split into factions. One camp basically yelled, “That’s not a feature, that’s guilt management” — with one commenter roasting the “soft approval” idea as a way to feel better while approving code you secretly hate. Another crowd swooped in with the classic internet response: this already exists. A fan of tangled.org popped up like an indie band evangelist insisting the future is already here if people would just look. Then came the practical crowd, coolly pointing out that some of the author’s dream features already have existing workarounds.
And hovering over all of it was the juiciest subplot: a growing sense that GitHub may have become the solution that turned into the problem. Some readers smell a disruption moment. Others just want the opposite of a mega-platform — a dead-simple place to upload projects and leave all the extra bells, whistles, and corporate workflow theater behind.
Key Points
- •The article says GitHub, GitLab, and Gitea share a broadly similar forge design, with GitHub setting many industry patterns.
- •The author describes Git as originally designed for decentralized, maintainer-driven workflows such as kernel development via emailed patches.
- •The piece argues that in many workplaces Git is mainly used to sync with a centralized forge, while review, CI, identity, issue tracking, and releases happen on the platform.
- •One proposed improvement is to move feedback earlier by running enforced remote checks before code is pushed, rather than after a pull request is opened.
- •The article also argues that pull-request approval is too binary and references Gerrit as an example of a more nuanced review approach.