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's queue learned to merge stacked pull requests, then spent August tightening the edges.

merge-queueci-automationgithubstacked-prsdeprecationsfork-security
◆Current state
Mergify automates merge queues for GitHub, and August was a mix of one real capability and a batch of contract cleanup. The queue can now merge GitHub-native stacked pull requests in order, speculative-check budgets apply per lane across dynamic scope sets, and conditions can match on whether a pull request came from a fork. Alongside that, the badge API was removed, pagination stopped advertising first and last links, and author-run commands were restricted to fork pull requests by default.
◆Where it's heading
Two threads. The queue is absorbing workflows that used to sit outside it - stacked pull requests, flaky-test detection and rerunning within a CI budget - which pushes Mergify from a merge gate toward owning the whole pre-merge pipeline. The other thread is a deliberate narrowing of surface: deprecated endpoints removed, the github_actions action marked for removal in March 2027, default command permissions tightened around forks. That is a product trimming what it maintains so the queue can take on more.
◆Prediction
Expect more of the pre-merge pipeline to move inside the queue on the flaky-test pattern, and further deprecations of automation that overlaps with what GitHub Actions now does natively.

◆Recent moves

  1. 8d ago

    Per-lane check capacity for dynamic scopes

    A single speculative-check budget can now apply across every scope, so dynamic scope sets get per-lane capacity without enumerating scope names. Configuration catching up to teams whose scopes are generated rather than listed.

    View source ↗
  2. 8d ago

    Pagination drops the first and last links

    Paginated API responses advertise only next and prev, and drop the Link header entirely when neither exists. A contract change more than a feature - clients that walked first or last links need updating.

    View source ↗
  3. 8d ago

    Repository badge API removed

    The deprecated /v1/badges/* endpoints are gone and embedded README badges no longer render. Part of the same August trimming as the pagination change and the github_actions deprecation, and the most visible of them since it breaks a public page.

    View source ↗
  4. 8d ago

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

    Dequeue reasons now carry GitHub's own refusal message, including the repository rule that blocked the push. Diagnostic detail rather than capability, but it turns an opaque queue rejection into something a maintainer can act on.

    View source ↗
  5. 21d ago

    Merge GitHub stacked pull requests with the merge queue

    ⚡ SPARK

    The merge queue takes on stacked pull requests, ordering them through GitHub's own merge API. For a product whose entire job is the merge gate, this closes the workflow that most often forced teams to bypass it.

    View source ↗
  6. 22d ago

    New from-fork condition attribute

    Conditions can now match on whether a pull request comes from a fork. A small predicate, but it is the primitive behind the same day's tightening of author-run commands, which now default to fork pull requests only.

    View source ↗