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

gitea-mq review

Free#12 of 26 in Merge Queue Software

An open-source queue that validates pull requests in batches before they merge.

7.1/10Editor score
gitea-mq7.1 Visit gitea-mq

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

gitea-mq manages pull-request merge queues for Gitea and GitHub repositories. It suits teams that want to validate changes before merge without adopting a hosted queue product, including small, mid-market, and enterprise teams comfortable running a service themselves. Changes enter through a forge’s auto-merge workflow or a configured merge label, and a web dashboard displays queue status and check results.

Its standout capability is batch validation: gitea-mq can test multiple queued pull requests together on temporary merge branches, then bisect a failing batch and remove the failing pull requests. That can reduce repeated validation work when a queue contains several changes. A health endpoint supports monitoring, and managed Gitea repositories can be discovered by topic. The project documents integrations with Gitea, GitHub, and Forgejo, while its stated backend support covers Gitea and GitHub; teams using GitLab or Bitbucket should look elsewhere.

The project is open source and has a free plan, with no paid tiers described. Deployment is self-hosted as a service or container, requires PostgreSQL, and includes a documented NixOS module for configuration. Documentation is the listed support channel, so teams should be prepared to handle deployment and operations themselves. Choose gitea-mq if your forge is supported and you value configurable batch checks and queue visibility; it is a weaker fit if you need a hosted offering, other forge backends, or support beyond docs.

gitea-mq pros and cons

  • Where it wins
    • Tests queued pull requests on temporary merge branches.
    • Batches pull requests and bisects failing batches to isolate changes.
    • Dashboard shows queue state and check results across Gitea and GitHub.
  • Where it doesn't
    • Supports Gitea and GitHub, but not GitLab or Bitbucket.
    • Requires PostgreSQL and a self-hosted service or container.
    • Support channels are limited to documentation.

gitea-mq 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