glmt review
A free, interactive GitLab CLI queue with eligibility checks and merge-train support.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
glmt is an open-source, local terminal interface for selecting and sequentially merging GitLab merge requests. It is aimed at GitLab users, including GitLab Free users, who want to choose an order for eligible requests without deploying a server, configuring labels, or using webhooks. The interactive interface shows request eligibility and reasons for ineligibility, including approval, pipeline, conflict, and discussion status. Its local, self-hosted approach suits small and mid-market teams comfortable working from a terminal, rather than teams looking for a hosted queue service.
The queue focuses on controlled sequencing rather than batch validation. Users select and order requests; glmt rebases each one onto the target branch before merging. A SHA guard helps catch a changed branch state, with one rebase retry after a SHA mismatch. Requests with rebase conflicts are skipped without stopping the rest of the queue. Stacked merge requests are supported in a train, and after processing, glmt waits for the final main-branch pipeline and displays its status. This makes it a fit when ordered merges and visibility into eligibility matter more than parallel validation or broader automation.
glmt integrates with GitLab and the glab CLI, and runs on Linux, macOS, and Windows. It is free, so there are no paid tiers to weigh; its scope is specifically GitLab rather than GitHub or Bitbucket. Support is through documentation. Choose glmt if a local, interactive sequential workflow fits how your team handles merge requests. Look elsewhere if you need hosted operation, batch validation, or automation beyond the queue behavior described here.
glmt pros and cons
- Where it wins
- Shows merge-request eligibility and why a request is ineligible.
- Rebases requests in order, with a SHA guard and one retry on mismatch.
- Supports stacked merge requests and waits for the final main-branch pipeline.
- Where it doesn't
- Supports GitLab rather than GitHub or Bitbucket.
- Skips requests with rebase conflicts instead of resolving them in the queue.
- Does not provide hosted batch validation or detailed automation options.
glmt 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