Concepts

You work on one local branch with multiple commits. Mergify Stacks maps each commit to its own GitHub pull request. The PRs are chained together: each one’s base branch is the previous PR’s head branch.

Reviewers see one small, focused diff per PR instead of the accumulated changes of the entire branch.

When you run mergify stack push, each commit goes through three stages:

Your local commits become remote branches, and each remote branch becomes a pull request. The Change-Id in each commit message is what ties all three together.

The Change-Id connects your local commits to their corresponding pull requests. It’s a unique identifier embedded as a Git trailer in each commit message:

feat: add user authentication

Implement JWT-based auth with refresh tokens.

Change-Id: Ia1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2

The Change-Id is:

• Generated automatically by a commit-msg Git hook installed during setup

• Persistent across rebases, amends, and history rewrites

• The mapping key that Stacks uses to know which commit corresponds to which PR, even after you rewrite your branch

You never need to manage Change-Ids manually. They’re created once and preserved through all git operations.

When you run mergify stack push, each commit gets its own remote branch. The naming convention is:

stack/{username}/{branch-name}/{Change-Id}

For example, if user alice pushes a branch called feat/auth with 3 commits:

You can customize the branch prefix via Git config:

git config mergify-cli.stack-branch-prefix "my-prefix"

Each PR targets the previous PR’s branch as its base, creating a dependency chain:

Stacks also adds a Depends-On: #NNN reference in each PR description and posts a stack comment on every PR listing the full chain:

The stack comment shows where each PR sits in the chain, with links to jump between them. This gives both authors and reviewers a clear map of the entire change.

When you push again after making changes, Stacks doesn’t recreate everything. It compares each commit’s Change-Id and SHA against what’s already on GitHub:

• Changed commits get their PR updated (force-push to the remote branch)

• Unchanged commits are skipped entirely

• Removed commits (after squashing or dropping) get their orphan remote branches deleted automatically

mergify stack push is always safe to run. It only does the minimum work needed to sync your local branch with GitHub.

See Setup to install the CLI and configure your repository.