Merge Queue Action

At a glance

• Editor score
  6.5 / 10
• Pricing
  Free plan
• Best for
  GitHub teams wanting a minimal label-driven merge queue
• Free plan
  Yes
• Paid from
  Free
• Batch validation
  No
• Facts checked
  23 Oct 2026

• Where it wins

  • Queues pull requests by repository label and marks queue status.
  • Updates an out-of-date pull request before merging.
  • Advances to the next pull request after the active one leaves merging status.

• Where it doesn't

  • Works with GitHub rather than GitLab or Bitbucket.
  • Does not validate multiple queued pull requests together.
  • Requires a GitHub workflow and a repository-permission personal access token.

Our verdict on Merge Queue Action

Merge Queue Action is an open-source GitHub Action for teams that want pull requests merged sequentially. Maintainers add a repository label to queue a request; the action marks one as actively merging and labels the others as queued. It is aimed at GitHub maintainers who want a minimal queue workflow rather than a broader merge-management system. The project is free and open source, with its behavior centered on moving one pull request through the queue at a time.

The queue checks whether the active pull request is up to date and updates it before merging if needed. It merges after required checks pass, and removes the request from active merging status if required checks fail. Once the active request leaves that status, the next queued pull request is processed. The project documentation says required checks from CircleCI are supported and requires a base branch with a required check. This makes it relevant to teams using GitHub Actions alongside CircleCI, while the documented workflow remains specific to GitHub.

Setup requires a GitHub workflow and a personal access token with repository permissions. The scope is deliberately narrow: it does not describe validating multiple queued pull requests together or using merge trains, and it does not support GitLab or Bitbucket. Choose Merge Queue Action if label-driven, sequential merging covers your needs and you are comfortable configuring the workflow and token. Teams that need batch validation, merge trains, or queue support beyond GitHub should look elsewhere.

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

Merge Queue Action pricing

Merge Queue Action fact sheet

Merge Queue Action integrations

Merge Queue Action lists 2 integrations on its own site.

• GitHub
• CircleCI

Alternatives to Merge Queue Action

• 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 Action alternatives →

Featured on iTechGuides

Merge Queue Action 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-action/"><img src="https://www.itechguides.com/best/badge/merge-queue-action.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