Maiao: Gerrit-style code review workflow for GitHub, GitLab, Gitea, others
26 points by zdw 4 hours ago | 8 comments

NamlchakKhandro 10 minutes ago
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?

reply
what 2 minutes ago
Why would you have more than one commit for a PR? That sounds like crazy town.
reply
jsphweid 3 minutes ago
1 commit == 1 reviewable unit == 1 PR == 1 CL == 1 feature == 1 fix is a perfectly reasonable way of working.

I used to work at companies where no one squashed their commits and the entire git logs were filled with 80% non-sense like "temp" or "bad" or "working" with the other 20% being coherent changes. What's the point of doing this I ask?

reply
steveklabnik 8 minutes ago
This is standard practice in the "stacked diffs" world: one review, one commit.
reply
jasonlotito 22 minutes ago
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.
reply
esafak 2 hours ago
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.

reply
dietr1ch 50 minutes ago
It seems so, https://github.com/runetes/maiao#quick-example

As they say in mtg, reading the card explains the card

reply
martythemaniak 56 minutes ago
Gerrit. Now that's a name I've not heard in a long time. A long time
reply