Mergify CLI
Drive Mergify from your terminal and CI pipelines:
stacked pull requests, the merge queue, CI Insights, scheduled freezes, and
configuration — all from a single self-contained binary that reuses your
existing GitHub (gh) login.
mergify stack push # turn your local commits into stacked PRs
mergify queue status # inspect the merge queue
mergify ci junit-process report.xml # upload test results to CI Insights
- One static binary. No runtime, no dependencies — drop it on a developer laptop or a CI runner and go.
- One command to sign in.
mergify auth loginapproves the CLI in your browser and keeps the credential in your OS keychain;MERGIFY_TOKENor--tokenfor scripting. - Built for pipelines. Logs to stderr, structured
--jsonoutput on read commands, and stable exit codes for scripts and runbooks. - Cross-platform. Linux, macOS (x86_64 + aarch64), and Windows.
Installation
Homebrew (recommended for macOS)
brew install mergifyio/tap/mergify-cli
The fully-qualified name taps and installs in one step. Upgrade with
brew upgrade mergify-cli — not mergify self-update, which overwrites the
Homebrew-managed binary. See the tap
for tap-trust and short-name details.
Install script (recommended for Linux; also macOS — x86_64 and aarch64)
curl -fsSL https://raw.githubusercontent.com/Mergifyio/mergify-cli/main/install.sh | sh
Installs to ~/.local/bin/mergify. Override with MERGIFY_INSTALL_DIR=/usr/local/bin
or pin a version with MERGIFY_VERSION=<version>. Upgrade with mergify self-update.
Manual download (Windows, or to bypass the script)
Grab the matching archive from the latest release:
- Windows — download
mergify-<version>-x86_64-pc-windows-msvc.zip, extract it, and putmergify.exeanywhere on yourPATH. - Linux / macOS — download
mergify-<version>-<target>.tar.gz(e.g.mergify-2026.10.1-aarch64-apple-darwin.tar.gz), extract withtar -xzf, and put the resultingmergifybinary anywhere on yourPATH.
Verify against SHA256SUMS from the same release if you care.
Authentication
Sign in once:
mergify auth login
It opens the approval page in your browser, and prints the URL and the code
as well: pass --no-browser, or run it where there is no browser to open,
and the printed pair is all you need. Once you approve, the
credential lands in your OS keychain — or, on a machine with none (a
container, an unattended agent, a headless box with no D-Bus session), in a
restricted file under your configuration directory. mergify auth status says
which account you are signed in as, and mergify auth logout asks the Mergify
API to revoke the credential rather than only deleting the local copy.
The approval page labels the new token Mergify CLI on <hostname>. Pass
--device-name "work laptop" to name the machine yourself, or --device-name=
to keep the hostname from leaving the machine at all.
The commands that talk to the Mergify API resolve a credential in this order:
| # | Credential | |
|---|---|---|
| 1 | --token / -t |
|
| 2 | MERGIFY_TOKEN |
|
| 3 | the credential stored by mergify auth login |
keyed by API URL |
| 4 | GITHUB_TOKEN |
deprecated |
| 5 | gh auth token |
deprecated |
A GitHub token still authenticates against the Mergify API and prints a
deprecation warning once per run. It will stop working in a future release;
run mergify auth login instead. In CI, set MERGIFY_TOKEN — nothing about
that changes.
mergify ci skips step 3. Those endpoints require an organization
application key, which is what MERGIFY_TOKEN holds in a CI job; the
per-user credential mergify auth login mints is refused there by design.
mergify stack also calls the GitHub API directly, and resolves that
token separately (--token, MERGIFY_TOKEN, GITHUB_TOKEN, gh auth token). It is unaffected by the deprecation above: stack needs a GitHub
credential and Mergify never issues one. A Mergify-issued token (mut_…) is
skipped there rather than sent to GitHub, which would only answer 401 Bad credentials — in MERGIFY_TOKEN, in GITHUB_TOKEN, and in what gh auth token returns, since it echoes GITHUB_TOKEN when that is set. Only an
explicit --token is sent as given.
The repository and API URL resolve as before:
| What | --flag |
then env | then |
|---|---|---|---|
| Repository | --repository / -r |
GITHUB_REPOSITORY |
git remote (origin) |
| API URL | --api-url / -u |
MERGIFY_API_URL |
https://api.mergify.com |
Credentials are stored per API URL, so one machine can hold a credential for the hosted service and one for an on-premise install.
Mergify application keys come in two classes, each reaching its own set of
endpoints rather than one being a subset of the other. A ci key is scoped
to what a CI job does — trace upload, ci scopes-send, quarantine evaluation
and the quarantine list. Trace upload and ci scopes-send take a ci key
only, and answer an admin key or a user credential with 403 Forbidden.
Reading test health (mergify tests show) and changing the quarantine
(mergify tests quarantines add / remove) need an admin key or a user
credential — the one mergify auth login stores, or a GitHub PAT — and
answer a ci key with 403 Forbidden. Note that GITHUB_TOKEN inside
GitHub Actions is the ephemeral installation token, not a PAT, and does not
reach the Mergify API.
See the authentication guide for details.
Quick start
# Stacked pull requests — one PR per commit, kept in sync
mergify stack setup # once per repo: install the git hooks the stack needs
mergify stack push # push commits and create/update their PRs
mergify stack list # show the stack and its PR status
mergify stack sync # rebase the stack onto its trunk
# Merge queue
mergify queue status # current queue state for the repo
mergify queue status --json # same, as machine-readable JSON
# CI Insights — from inside your pipeline
mergify ci junit-process report.xml --test-language python
# Configuration
mergify config validate # check .mergify.yml against the schema
Run mergify --help for the full command list and mergify <command> --help
for any command's flags.
Commands
Every command group maps to a section of the CLI reference.
mergify auth— Sign in to Mergify and manage the stored credential (login,logout,status).mergify stack— Create and maintain stacked pull requests. Docsmergify queue— Inspect and control the merge queue. Docsmergify events— Browse the events Mergify recorded for the repository or one pull request, as a timeline or JSON.mergify ci— Send JUnit results and pull request scopes from any CI provider. Docsmergify tests— Look up test health and manage the flaky-test quarantine. Docsmergify freeze— Schedule merge freezes for release windows and maintenance. Docsmergify config— Validate your configuration and simulate actions before you merge. Docsmergify self-update— Update the CLI to the latest release.mergify completions <shell>— Print a shell completion script (see below).
Run mergify <command> --help for a group's subcommands and flags.
Shell completions
Generate a completion script for your shell — bash, zsh, fish,
elvish, or powershell:
# zsh — write to a directory on your $fpath
mergify completions zsh > ~/.zfunc/_mergify
# bash — load in your current session (add to ~/.bashrc to persist)
source <(mergify completions bash)
# fish
mergify completions fish > ~/.config/fish/completions/mergify.fish
Global options
These are accepted on every command:
| Flag | Description |
|---|---|
-v, --verbose |
Increase log verbosity: -v info, -vv debug, -vvv trace. Logs go to stderr so stdout stays pipeable. |
--debug |
Shorthand for at least debug-level logging (like -vv). |
--color <auto|always|never> |
When to colorize terminal output. |
Environment variables
| Variable | Effect |
|---|---|
MERGIFY_TOKEN |
API token. Takes precedence over a stored mergify auth login credential. |
GITHUB_TOKEN |
Deprecated as a Mergify API credential (falls back to gh auth token); still the GitHub token mergify stack uses. |
GITHUB_REPOSITORY |
Default owner/repo when --repository is omitted. |
MERGIFY_API_URL |
API base URL (default https://api.mergify.com). |
RUST_LOG |
Fine-grained log filtering; overrides --verbose. |
NO_COLOR |
Disable colored output. Must be set to a non-empty value; exported-but-empty counts as unset. |
FORCE_COLOR, CLICOLOR_FORCE |
Force colored output when it would otherwise be off. Same non-empty rule, and NO_COLOR wins over both. All three apply to --color auto only. |
MERGIFY_INSTALL_DIR, MERGIFY_VERSION |
Install-script target directory / pinned version. |
Exit codes
Commands return stable exit codes so scripts and runbooks can branch on them:
| Code | Meaning |
|---|---|
0 |
Success. |
1 |
Unclassified runtime failure (I/O error, bug, or captured panic). |
2 |
Argument parsing / usage error. |
3 |
Stack, branch, or commit not found. |
4 |
Rebase or merge conflict. |
5 |
GitHub API request failed. |
6 |
Mergify API request failed. |
7 |
CLI invariant violated (e.g. run outside a valid context). |
8 |
Configuration or credentials missing, unparseable, or failing validation (including "not logged in"). |
AI Agent Skills
Mergify CLI provides AI skills for managing stacked PRs and Git workflows, compatible with Claude Code, Cursor, and many other AI agents.
Install via npx (all agents):
npx skills add Mergifyio/mergify-cli
Install as a Claude Code plugin:
/plugin install mergify@claude-plugins-official
Documentation
Full reference and guides live at docs.mergify.com/cli.
Contributing
Bug reports and feature requests are welcome: open an
issue. The CLI is developed
by Mergify; this repository publishes it: the releases, the installer, the
agent skills and this README, all updated with each release. Suggestions to
install.sh, skills/ or the documentation are welcome as issues too. See
AGENTS.md for what lives where.
License
Proprietary — see LICENSE. Use is governed by the Mergify Terms of Service.
Metadata
Release files for mergify-cli 2026.10.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| mergify_cli-2026.10.4-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details |
| mergify_cli-2026.10.4-py3-none-musllinux_1_2_x86_64.whl | Python 3 | none | Linux musl 1.2+ x86-64 | Details |
| mergify_cli-2026.10.4-py3-none-musllinux_1_2_aarch64.whl | Python 3 | none | Linux musl 1.2+ ARM64 | Details |
| mergify_cli-2026.10.4-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | Python 3 | none | Linux glibc 2.17+ x86-64 | Details |
| mergify_cli-2026.10.4-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl | Python 3 | none | Linux glibc 2.17+ ARM64 | Details |
| mergify_cli-2026.10.4-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details |
| mergify_cli-2026.10.4-py3-none-macosx_10_12_x86_64.whl | Python 3 | none | macOS 10.12+ x86-64 | Details |
Total release size: 48.3 MB
Release files / mergify_cli-2026.10.4-py3-none-win_amd64.whl
| Download URL | mergify_cli-2026.10.4-py3-none-win_amd64.whl |
|---|---|
| Size | 6.5 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
25e6313f3970a55393bcaf15997d488cb1a35d514d4cbaa5c8460a27370eaae3
|
|
BLAKE2b-256 checksum How to use checksums |
f255c3cde20f9a641ad8a44cf2c057bd6668ba8988403120c6f19911065ef2b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.
Transparency logRelease files / mergify_cli-2026.10.4-py3-none-musllinux_1_2_x86_64.whl
| Download URL | mergify_cli-2026.10.4-py3-none-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 7.7 MB |
| Tags | Linux musl 1.2+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
351b578be3176af7bb4c73f5c9dab3cec687438a67679480ab84a4e21aaaa0cc
|
|
BLAKE2b-256 checksum How to use checksums |
279a3e78aa4cb492cd132a8a30b909e7528043a287cd421aaf3057a3665ba7b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.
Transparency logRelease files / mergify_cli-2026.10.4-py3-none-musllinux_1_2_aarch64.whl
| Download URL | mergify_cli-2026.10.4-py3-none-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 7.1 MB |
| Tags | Linux musl 1.2+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
9cee2ee868f675db26121070578aa1919e0d09225b9117dbfd4dadacecdc3961
|
|
BLAKE2b-256 checksum How to use checksums |
9ca348f2589e9009e8b7d77c5315ce9a0469406064d0cf3a3e8bc12b3b2d34ce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.
Transparency logRelease files / mergify_cli-2026.10.4-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | mergify_cli-2026.10.4-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 7.6 MB |
| Tags | Linux glibc 2.17+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
b428d7046d2668a693f01673119a73e6caf8034c728d02d5b5c89b9e4176464f
|
|
BLAKE2b-256 checksum How to use checksums |
2bc2fbbe044483fce13d097ca2d0d2c813049dd8f3c8f93297311c7f0047a40f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.
Transparency logRelease files / mergify_cli-2026.10.4-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | mergify_cli-2026.10.4-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 7.1 MB |
| Tags | Linux glibc 2.17+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
e325d7beb1a49e67407bc258aefd2b60c3feb16655e241205e1c5d3b81f5b356
|
|
BLAKE2b-256 checksum How to use checksums |
a60dc590ea36859e3289f60296175c0377afdc55e0cc6bee7bd045510b5c9181
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.
Transparency logRelease files / mergify_cli-2026.10.4-py3-none-macosx_11_0_arm64.whl
| Download URL | mergify_cli-2026.10.4-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 6.0 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
68555c1c63718cea5570b3840a20050786e748c38b782735b4a2cfc8ac1262f0
|
|
BLAKE2b-256 checksum How to use checksums |
cdaddf6e7cda7f7543d06f90fd6fd2a538bf70c24627480197a2668a02ecb799
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.
Transparency logRelease files / mergify_cli-2026.10.4-py3-none-macosx_10_12_x86_64.whl
| Download URL | mergify_cli-2026.10.4-py3-none-macosx_10_12_x86_64.whl |
|---|---|
| Size | 6.4 MB |
| Tags | Python 3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
8f7c1518c4e8c3082e9c6537f1cb16e823fe776122349b36820ca388fc653610
|
|
BLAKE2b-256 checksum How to use checksums |
d19a8dc4ba4ce24136644207190deebefd36329e43eea084981e04b47a483d2f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.
Transparency log
