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

staqd review

Free#21 of 26 in Merge Queue Software

An open-source, self-hosted tool for merging GitHub pull-request stacks and restacking branches.

6.2/10Editor score
Visit staqd
staqd6.2 Visit staqd

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

For GitHub teams working with dependent pull requests, staqd manages stacked PR workflows through GitHub Actions and pull-request comments. It is open source and self-hosted, with no separate SaaS service or required CLI. Its focus is maintaining stack relationships: it can discover a stack from pull-request base branches, merge one PR and restack its children, or process a stack sequentially with approval checks.

Setup involves adding a reusable GitHub workflow or composite action and configuring repository permissions; GitHub App credentials are optional. The integration set centers on GitHub Actions, GitHub pull requests, the GitHub API, and Git. Commands targeting the same base branch are serialized, and after a parent PR is manually merged in GitHub, staqd can update child PR base branches. These choices suit teams already organizing work as GitHub PR stacks, rather than teams seeking a service spanning multiple repository hosts.

The project reports restack conflicts and provides manual fix commands, which gives maintainers a path to address conflicts instead of treating every stack operation as automatic. Its scope is narrower than a general merge queue: it does not offer batch validation or merge trains. Choose staqd when stack discovery, sequential merging, and child-branch maintenance are the priority; teams that need those broader queue workflows or support for GitLab or Bitbucket should look elsewhere.

staqd pros and cons

  • Where it wins
    • Discovers stack relationships from pull-request base branches
    • Merges a stack sequentially with approval checks
    • Restacks child branches and reports conflicts with manual fix commands
  • Where it doesn't
    • Requires setup as a GitHub Actions reusable workflow or composite action
    • Targets GitHub; GitLab and Bitbucket are not supported
    • Does not provide batch validation or merge trains

staqd 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