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

Anubis review

Free#16 of 26 in Merge Queue Software

An open-source GitHub bot for teams that want guarded, sequential merges.

6.7/10Editor score
Anubis6.7 Visit Anubis

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Anubis is an open-source Node.js bot for automatically merging ready GitHub pull requests. It is aimed at small teams that want eligibility checks, configured approval rules, and sequential merging without relying on a hosted merge service. The bot runs as a GitHub webhook on a server the team hosts, using a configured GitHub account and repository. Its scope is deliberately GitHub-specific, so teams working across GitLab or Bitbucket should look elsewhere.

Its workflow centers on staging: Anubis checks whether a pull request meets configured eligibility conditions, then places eligible work on a bot-maintained branch for CI validation. Once the configured checks and approvals pass, it merges validated pull requests in ascending PR-number order. Teams can set core-developer approval thresholds and waiting periods, and labels communicate processing and failure states. Squash-style commits use the pull-request title and description. This fits teams that value a clear, guarded sequence; it is less suited to repositories that need batch validation or a merge train, which are not documented capabilities.

Anubis offers dry-run, staged-only, and guarded-run modes, giving maintainers ways to inspect or constrain its behavior. That control is useful when adopting an automated merge process, but deployment still means operating the bot on a server and configuring its GitHub account and repository. The project provides documentation as its support channel. Choose Anubis if your team can self-host and wants sequential GitHub merges shaped by CI, approvals, and waiting rules. Choose another approach if you need a hosted service, support for another Git platform, or batch-based merge validation.

Anubis pros and cons

  • Where it wins
    • Stages eligible pull requests on a bot-maintained branch for CI checks
    • Merges validated pull requests in ascending PR-number order
    • Offers dry-run, staged-only, and guarded-run modes
  • Where it doesn't
    • Works with GitHub, not GitLab or Bitbucket
    • Does not document batch validation or merge trains
    • Requires a server you host and a configured GitHub account

Anubis 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