runetes/maiao

Source: https://github.com/runetes/maiao

Maiao

Note: This is a community fork of adevinta/maiao. The original maintainers are no longer at Adevinta and the upstream repository is no longer actively maintained. This fork continues development under runetes/maiao.

Gerrit-style code review workflow for GitHub, GitLab, Gitea, Forgejo, Bitbucket Cloud, and Cursor Origin

Maiao brings the power of stacked pull requests (or merge requests) to your git hosting provider, enabling you to break large features into small, reviewable commits where each commit becomes its own PR/MR.

What is Maiao?

Maiao provides the git review command that:

• Creates one PR/MR per commit in your branch
• Stacks PRs/MRs automatically with proper parent-child dependencies
• Registers native stacks when available (GitHub Stacks, GitLab auto-detected stacks)
• Manages fixups elegantly using git commit --fixup
• Tracks commits via Change-IDs (using the Gerrit commit-msg hook)
• Auto-rebases your stack when PRs/MRs get merged
• Auto-detects your provider from the remote URL

Supported Providers

Maiao auto-detects the provider from your remote URL for known hosts (github.com, gitlab.com, codeberg.org, bitbucket.org, origin.cursor.com). For self-hosted instances, it prompts on first use and saves the choice to git config maiao.provider.

Quick Example

# Make multiple commits
git commit -m "Add user authentication"
git commit -m "Add authorization middleware"
git commit -m "Add admin endpoints"

# Create stacked PRs/MRs for all commits
git review

Result: Three PRs/MRs created and stacked:

• PR #1: Add user authentication → main
• PR #2: Add authorization middleware → PR #1
• PR #3: Add admin endpoints → PR #2

Key Benefits

• Granular Reviews: Each commit reviewed independently for faster, focused feedback
• Clear History: One logical change per PR/MR maintains clean git history
• Easy Fixups: Address review feedback with git commit --fixup <sha>
• Automatic Stacking: Tool manages PR/MR dependencies automatically
• Native Stacks: Integrates with GitHub Stacks and GitLab’s auto-detected stacks
• Merge Detection: Stack updates automatically when PRs/MRs merge
• Rebase Integration: Handles upstream changes gracefully
• Multi-Provider: Works across GitHub, GitLab, Gitea, Forgejo, Bitbucket Cloud, and Cursor Origin

Native GitHub Stacks

Maiao treats GitHub native stacks as a progressive enhancement. When two or more PRs are pushed, Maiao probes the Stacks API (cached for 24 hours) and registers the PRs as a stack if supported. On older GitHub Enterprise instances the feature is silently skipped — branch-based stacking still works as before.

# Control via git config (default: auto)
git config maiao.useNativeStack auto   # use when available, skip otherwise
git config maiao.useNativeStack true   # always register; warn if unavailable
git config maiao.useNativeStack false  # disable entirely

Documentation

• Getting Started - Installation and workflow guide
• How Does It Work - Technical details and architecture
• Pricing - Free and open source

Learn About Stacked Diffs

Maiao implements the stacked diffs methodology. Learn more:

• Stacked Diffs Versus Pull Requests - Jackson Gabbard’s foundational article on the philosophy
• Graphite’s Guide to Stacked Diffs - Comprehensive guide to the workflow and best practices
• The Pragmatic Engineer: Stacked Diffs - Industry analysis and adoption patterns (paywalled)

Why “Maiao”?

As Maiao encourages users to create smaller and nicer commits in their pull requests, it has been given the name of a tiny island:

Contributing

Contributions are welcome! See CONTRIBUTING.md for details.

License

MIT License - see DISCLAIMER.md for details.