May 1, 2026
Pull request? More like pull the drama
If I Could Make My Own GitHub
Man dreams of fixing GitHub, but the comments instantly turn into a post-credit feud
TLDR: A writer imagined a cleaner, less frustrating alternative to GitHub, arguing that today’s code-sharing sites make simple work harder than it should be. But the comments stole the spotlight, with users redirecting the whole discussion elsewhere and sparking a mini fight over who posted it first.
A programmer’s fantasy about building a better version of GitHub — the giant website where coders store and review code — should have been a straightforward rant about clunky tools and tired workflows. Instead, the real fireworks came from the community, where the conversation practically teleported away mid-party. The author lays out a wish list for a richer, smarter code-hosting site: fewer messy late-night “fix” updates, more flexible approvals, and less of the rigid yes-or-no gatekeeping that makes modern software work feel like a bureaucratic obstacle course. It’s part tech manifesto, part billionaire daydream, complete with jokes about submarines, Wyoming compounds, and rocket-fueled vanity projects.
But in the discussion, the loudest reaction wasn’t even about the ideas — it was about where the comments went. One user bluntly announced that the entire chat had moved to Hacker News, which gave the whole thing the energy of a party host yelling, “We’re all going somewhere else!” Then came the tiny but delicious bit of forum drama: another commenter popped up to ask why their own submission wasn’t treated as the original post. It’s not a screaming scandal, but it’s exactly the kind of petty internet turf war that commenters live for.
So yes, there’s a serious complaint here: today’s coding platforms feel bloated and awkward. But the community mood was pure meta-chaos — less “let’s debate the future of software” and more “wait, whose thread is this anyway?”
Key Points
- •The article presents a hypothetical design for a new software forge inspired by dissatisfaction with current GitHub-style platforms.
- •It identifies GitHub, GitLab, and Gitea as modern forges that largely follow the same overall design model.
- •The article contrasts git’s original decentralized, email-based workflow with the centralized forge-based workflows common in many jobs.
- •It states that activities such as pull requests, CI testing, identity verification, issue tracking, and releases now happen mainly inside the forge rather than in git.
- •The author highlights three main problems with current forges in the excerpt: feedback arriving after commits, overly binary pull request approvals, and inflexible review requirements for pull requests.