Merge Queue for Stacked PRs

At a glance

• Editor score
  7.3 / 10
• Pricing
  Free plan
• Best for
  Teams merging stacked PRs as atomic batches
• Free plan
  Yes
• Paid from
  Free
• Batch validation
  Yes
• Facts checked
  23 Oct 2026

• Where it wins

  • Keeps a separate FIFO queue for each target branch.
  • Runs CI before merging stacked pull requests as atomic batches.
  • Retries branch-divergent runs and recovers stuck batches.

• Where it doesn't

  • Supports GitHub rather than GitLab or Bitbucket.
  • Requires self-hosting through GitHub Actions and repository configuration.
  • An admin break-glass label can bypass CI for immediate merges.

Our verdict on Merge Queue for Stacked PRs

Merge Queue for Stacked PRs is an open-source, self-hosted merge queue for GitHub repositories. It is aimed at small and mid-market teams that organize work in stacked or chained pull requests and want those changes validated and merged together. Separate FIFO queues for each target branch keep batches ordered, while CI runs before a stack is merged atomically. This is a focused tool for teams whose merge workflow centers on GitHub, rather than a general-purpose cross-platform queue.

Its strongest fit is the handling of stacked changes and the cases that can interrupt a merge. A hotfix label prioritizes an item, while retries—up to three times—address target-branch divergence during CI. The tool can detect and resume batches stuck in the completing state. Protected file paths can require per-path approvers, and an admin-only break-glass label allows immediate merging without CI. That emergency path is useful for operational control, but teams should decide carefully when bypassing validation is acceptable.

The published plan is Free and MIT-licensed, with self-hosting via a GitHub Actions workflow and repository configuration. Integrations include GitHub Actions and the GitHub API; optional metrics can use OTLP or Prometheus backends. That makes it a reasonable fit for teams comfortable maintaining their own workflow and seeking visibility into queue behavior. It is less suitable for organizations requiring GitLab or Bitbucket support, or a managed deployment. Choose it when atomic stacked-PR handling and recovery matter; consider another queue if broader platform support or managed service is a requirement.

Your product? Our editors can test Merge Queue for Stacked PRs in depth and publish a review, labelled as paid · from $149/mo →

Merge Queue for Stacked PRs pricing

All 1 Merge Queue for Stacked PRs plans and prices →

Merge Queue for Stacked PRs fact sheet

Merge Queue for Stacked PRs integrations

Merge Queue for Stacked PRs lists 4 integrations on its own site.

• GitHub Actions
• GitHub API
• OTLP
• Prometheus

Alternatives to Merge Queue for Stacked PRs

• MergifyMerge queues and stacked PRs paired with test-health tools and broad CI integrations.8.9
• BitbucketA practical fit for Bitbucket teams that want merge queues alongside code hosting and CI/CD.8.5
• ProwSelf-hosted CI and pull-request merge automation for teams running Kubernetes.8.1

See all Merge Queue for Stacked PRs alternatives →

Featured on iTechGuides

Merge Queue for Stacked PRs is listed in our Merge Queue Software directory. Add the badge to your site — it links back to this page.

<a href="https://www.itechguides.com/products/merge-queue-for-stacked-prs/"><img src="https://www.itechguides.com/best/badge/merge-queue-for-stacked-prs.svg" alt="Featured on iTechGuides" width="230" height="46"></a>

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated 30 Oct 2026 · How we research and update