Maiao: Gerrit-style code review workflow for GitHub, GitLab, Gitea, others
zdw
56 points
26 comments
August 25, 2026
Related Discussions
Found 5 related stories in 59.3ms across 4,390 title embeddings via pgvector HNSW
- Reviewing code you didn't write colescodes · 14 pts · July 22, 2026 · 48% similar
- Git at Any Scale meetpateltech · 30 pts · August 18, 2026 · 47% similar
- Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode yoanwaidev · 95 pts · July 30, 2026 · 47% similar
- Show HN: I canceled my AI code reviewer and wrote a free local one mukundzha6 · 22 pts · August 18, 2026 · 47% similar
- Game of Trees – Git-based version control from OpenBSD folks gregnavis · 59 pts · July 24, 2026 · 47% similar
Discussion Highlights (8 comments)
esafak
Does it use Github's new stacked PR feature? Edit: apparently stacked PRs on GH are older than I thought; the readme references a 2024 blog post about it.
martythemaniak
Gerrit. Now that's a name I've not heard in a long time. A long time
jasonlotito
As someone who much prefers Gerrit's UI/UX over GitHub's UI, I was disappointed that this wasn't replicating the UI for GH reviews. Edit: Just to be clear, this is not a blemish on this project. More a lament and a wish someone would create such a thing for those of us forced to leave Gerrit behind for... GitHub. =/
NamlchakKhandro
Who is creating a separate PR for each commit on their feature/fix branch? sounds like crazy town. I just dont understand why someone would operate like this. Lets assume you're squash merging your feature branchs to your local main, then you're raising the them as prs. why would you do this?
Kinrany
Is it compatible with jujutsu?
dolmen
The repo seems to move from "adevinta" (a well known company in the EU tech) to "runetes". Anyone to tell us the story?
ppljudge
This sounds intriguing. Additionally, I wanted the community to evolve our approach to providing PR feedback. One of the unintended consequences was that it became a tool for people to exploit their workers.
globular-toast
IME juniors struggle with making single commits in the first place. What I usually see is a scatter brained approach with more "fix" commits than anything else. This doesn't help with that, does it?