Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

GitHub Merge Queue review

Freemium#7 of 26 in Merge Queue Software

A GitHub-native FIFO queue for validating grouped pull requests before merging.

7.6/10Editor score
GitHub Merge Queue7.6 Visit GitHub

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

GitHub Merge Queue automates pull request merging on busy GitHub branches. Teams can queue pull requests in first-in-first-out order after required branch-protection checks pass; a user with write access adds them to the queue. It suits teams that need validation of incoming changes against the latest target branch and changes already ahead in the queue, rather than merging each pull request based only on an earlier check.

Validation runs required status checks through GitHub Actions or another CI provider. Teams can configure build concurrency from 1 to 100 merge_group webhooks, set status-check timeouts, choose minimum and maximum pull requests to merge together, and select merge, rebase, or squash. This gives teams control over how queued work is grouped and checked, while relying on their existing CI provider for the checks themselves. It is a focused fit for GitHub workflows, not a cross-hosting queue: the listed integrations are GitHub Actions and third-party CI providers.

The Free plan costs $0 per month and includes unlimited public and private repositories. The Team plan is $4 USD per user/month for the first 12 months, according to the vendor's pricing page; it adds repository rules, multiple pull request reviewers, and advanced collaboration for individuals and organizations. The product is cloud-based and lists community support. Choose it if FIFO validation on GitHub is the core need and the team can use its CI checks; consider an alternative if GitLab or Bitbucket support is required, or if the workflow depends on a merge train rather than the documented queue behavior.

GitHub Merge Queue pros and cons

  • Where it wins
    • Checks queued changes with the latest target and earlier queued changes
    • Works with GitHub Actions or third-party CI providers
    • Configures concurrency, check timeouts, merge limits, and merge methods
  • Where it doesn't
    • Limited to GitHub rather than GitLab or Bitbucket
    • Requires required branch-protection checks before queueing
    • Team plan's $4 per-user monthly price applies to the first 12 months

GitHub Merge Queue fact sheet, pricing and score →

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 · How we research and update