9/4/2026
Maiao: Gerrit-style code review workflow for GitHub, GitLab, Gitea, others
Filed by Patch Reyes
Gerrit devs who've been craving that blessed "review before merge" pipeline on modern forges finally have a reason to smile. Maiao bolts the Gerrit-style workflow onto GitHub, GitLab, Gitea, and friends—no need to abandon the platform your org already lives in. It's an open source tool that reproduces the change-based review model (think: rebase-friendly, patch-set-driven flow) without forcing you to run a Gerrit server from 2012. For teams tired of the "merge and regret" pull request dance, this is a serious shot at reclaiming review discipline. Early days, but the concept hits a nerve—81 points and 45 comments on HN says the demand is real.
P
Patch Reyes
Magazine AI commentary
Let's be honest: the modern pull request is a glorified pile-up. You push a branch, you wait, a human squints at a diff, you get yelled at for whitespace, you push again, and suddenly you're ten commits deep in a conversation about whether "fix typo" deserves its own commit. Gerrit had the right idea fifteen years ago: treat every change as a unit, make rebasing natural, and force reviewers to actually engage with the patch—not just the PR description. Maiao is essentially a time machine that brings that discipline forward into the ecosystems where developers actually live today.
What makes this interesting isn't the code—it's the admission that the code review UX across GitHub, GitLab, and Gitea has stagnated. Forge platforms compete on features, but the core review loop hasn't changed meaningfully in a decade. Maiao sidesteps the "wait for GitLab to add Gerrit-like reviews" problem by grafting the workflow on top, which is both its genius and its Achilles' heel. It's a shim, a duct-tape solution, and yet—maybe that's exactly what the ecosystem needs. Not another fork or platform migration, but a workflow layer that respects existing infrastructure.
The HN response (81 points, 45 comments) suggests real hunger here. The open source community has been in a "review theater" crisis: PRs that sit for weeks, CI that green-lights garbage, and maintainers drowning in notifications. Maiao doesn't solve the human problem—no tool can force people to review carefully—but it does remove the structural excuses. When rebasing is painful and review history is buried in a tab, bad review habits become institutionalized. This tool at least makes the right thing possible.
The bigger question for the OSS Report audience: is this a bridge to nowhere or a foundation? The Gerrit-style model is powerful but demanding—it requires more from reviewersatory than a casual thumbs-up. Teams that adopt this are self-selecting for rigorll, which is probably the real value proposition. It's not "unpopular opinion: Gerrit was right all along"—it's "the tools you already use can do better if you're willing to install a workflow layer." That's a low-cost experiment with potentially high payoff.
Biggest risk: as with any bolt-on, maintenance burden and ecosystem fatigue. But for a tool that exists primarily to change habits rather than platforms, Maiao is a refreshingly pragmatic take. Watch it, try it, and maybe—just maybe—your next PR won't feel like a game of survivor.
Source: https://github.com/runetes/maiao
📌 Read the real article ↗via Hacker News · Hacker News