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

Marge-bot review

Free#8 of 26 in Merge Queue Software

A GitLab-only merge bot for teams that want self-hosted CI and approval gates.

7.5/10Editor score
Marge-bot7.5 Visit Marge-bot

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Marge-bot automates GitLab merge requests: teams assign ready requests to the bot, which rebases each one against its target branch, waits for CI pipelines and configured approvals, then merges. Its optional batch mode groups requests for the same target, tests their combined changes on a temporary branch, and then merges the individual requests. This fits GitLab teams that want merge gates and batch testing without adopting a hosted service, including small, mid-market, and enterprise teams prepared to run the software themselves.

Batch testing is the standout feature for teams whose main concern is whether several changes work together before they merge. Marge-bot can also apply configurable embargo periods, filter requests by project and source or target branch, and add Reviewed-by, Tested-by, and Part-of commit trailers. After a push, it can impersonate approvers. Teams can run it as a service or scheduled GitLab CI job, with documented deployment options including a Python app, Docker container, or Kubernetes workload. That flexibility supports different self-hosted workflows, but leaves operation and deployment with the team.

The project is open source and has a free plan; the official documentation describes user-operated deployments rather than plan pricing. Its narrow ecosystem fit is decisive: it supports GitLab, not GitHub or Bitbucket, and it is not a merge train. The project page describes it as a community-driven fork reviving an unmaintained upstream project, a relevant maintenance consideration for teams evaluating reliability. Choose Marge-bot if GitLab support, self-hosting, and batch validation matter more than a hosted workflow or broader platform coverage; teams needing another Git provider should look elsewhere.

Marge-bot pros and cons

  • Where it wins
    • Rebases requests and waits for CI and configured approvals before merging
    • Batch-tests requests targeting the same branch on a temporary branch
    • Supports embargo windows, branch filters, and optional commit trailers
  • Where it doesn't
    • Supports GitLab only, not GitHub or Bitbucket
    • Requires teams to operate a self-hosted deployment
    • Community-driven fork of an unmaintained upstream project

Marge-bot 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