Mergify vs Cursor

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.

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.

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.