LoginSign Up
← Back to all sparks
M

Mergify

INFRA · APIS
Velocity6.3

Merge queue and pull request automation service for software teams

mergify.com ↗

Mergify tightens merge queue controls with deployment pinning, per-lane capacity, and GitHub-native stacked PR support.

merge-queueci-cddevtoolsgithubdeployment-gatingpull-requests
◆Current state
Mergify is shipping targeted capability additions to its merge queue around two themes: finer-grained deployment and scope controls, and tighter security around author permissions. Deployment conditions can now be pinned to specific apps, per-lane check capacity applies to dynamic scopes without enumerating scope names, and the stacked PR merge integration brings GitHub's native stacked PR feature into the merge queue. On the security side, head branch writes are now restricted to the originating repository and forks, preventing cross-repository writes.
◆Where it's heading
Mergify is expanding its merge queue from a queue-and-merge tool toward a fully controllable CI/CD gating layer. The deployment condition pinning, per-lane capacity limits, and stacked PR support each address specific enterprise workflow gaps rather than adding breadth. The Datadog metrics retirement (replacing custom metrics with a cleaner `mergify.queue.*` set) and badge API removal signal an API consolidation pass running in parallel with feature additions.
◆Prediction
Expect continued deepening of the deployment condition model — more condition attributes for filtering merge behavior based on deployment context and app identity. The stacked PR integration suggests GitHub's native stacked PR tooling is gaining enterprise adoption; Mergify may add more explicit stacked PR workflow controls beyond queue membership.

◆Recent moves

  1. 8d ago

    Head branch updates stay inside your repository and its forks

    Head branch updates now refuse to write to repositories the target was forked from — closing a security gap where update/rebase/squash actions could propagate changes upstream unintentionally. This is a correctness fix with real security implications for teams using fork-based workflows.

    View source ↗
  2. 8d ago

    Datadog integration: four merge queue metrics are being retired

    Four Datadog metrics are retired in favor of the `mergify.queue.*` set shipped in July — a cleanup that requires dashboard updates from teams using the old metrics, but represents an API consolidation rather than a capability change.

    View source ↗
  3. 12d ago

    Pin a deployment condition to the app that deployed

    Deployment conditions can now be pinned to the specific app that deployed an environment, using the `@ /` qualified form. This closes a gap where deployment-success conditions could pass based on a deployment from any app rather than the expected one — a meaningful precision addition for multi-app CD setups.

    View source ↗
  4. 22d ago

    Repository badge API removed

    The deprecated /v1/badges/* endpoints are removed — a README badge embedded via these endpoints will no longer render. A planned deprecation removal with no functional impact on merge queue behavior.

    View source ↗
  5. 22d ago

    Per-lane check capacity for dynamic scopes

    Per-lane check capacity now applies to dynamic scope sets without requiring scope names to be listed explicitly — a workflow improvement that makes capacity budgets manageable for queues with variable or auto-generated scopes.

    View source ↗
  6. 22d ago

    Clearer reason when the merge queue can't create the draft pull request

    The dequeue reason message now includes GitHub's own refusal message and the blocking repository rule — improved observability when the merge queue can't create a draft PR, previously requiring separate debugging.

    View source ↗