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

Build-Flow Labs Merge Queue review

Free#14 of 26 in Merge Queue Software

A focused FIFO queue for GitHub teams that want to manage merges on their own infrastructure.

6.9/10Editor score
Build-Flow Labs Merge Queue6.9 Visit site

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Build-Flow Labs Merge Queue is a self-hosted GitHub App that processes pull requests in queue order. It is aimed at GitHub teams that want a simple FIFO merge process managed on their own infrastructure. The queue can rebase pull requests against the latest base branch, wait for status checks, and merge when checks pass. Teams can add pull requests by label, comment, or API, and install the service across multiple repositories.

Its operating model is a central consideration: the operator deploys the service and supplies a PostgreSQL database and GitHub App credentials. In return, the tool provides per-repository controls for merge method, timeout, and triggers, along with an event history for queue activity. API endpoints can view, add, remove, or retry queue items and manage settings, which gives teams an alternative to queueing through labels or comments. The project is open source under the MIT license; its published information does not describe a commercial plan.

The product stays narrowly focused on GitHub. It does not support GitLab or Bitbucket, and there is no merge-train or batch-validation workflow, so teams that need those approaches should look elsewhere. Choose Merge Queue if your repositories are on GitHub and you want ordered merges with status-check gating while retaining deployment control. It is a weaker fit for teams seeking a managed service, support for several code-hosting platforms, or validation of batches before merging.

Build-Flow Labs Merge Queue pros and cons

  • Where it wins
    • Processes pull requests in order and rebases against the latest base branch
    • Waits for status checks and supports label, comment, or API queue entry
    • Offers per-repository settings, event history, and API queue management
  • Where it doesn't
    • Requires operator deployment, PostgreSQL, and GitHub App credentials
    • Supports GitHub only, not GitLab or Bitbucket
    • Has no merge trains or batch validation workflow

Build-Flow Labs 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