Forward-Future/DeployBot logo

Forward-Future/DeployBot

Free

面向 Codex、Claude Code、Cursor 及任意 MCP 客户端的 agent 托管式 GitHub 合并队列。代理可准备并评审 PR,最终合并决定权仍归用户;权限存于 GitHub 标签与认证评论,支持突发冻结、串行合并、累积集成 PR 与失败后暂停。

FreeFree tier
Type
Open Source

About Forward-Future/DeployBot

DeployBot is a provider-neutral GitHub merge queue for coding agents. Codex, Claude Code, Cursor, or any MCP client can prepare and review a pull request; the user keeps the final merge decision by saying deploy. DeployBot stores authority in GitHub labels and authenticated comments. It records deploy intent immediately, promotes the final exact reviewed head, freezes bursts, merges independent work back-to-back, scaffolds cumulative integration PRs, follows main through production, and pauses after failures. The base installation has no review-service dependency; repositories can use required checks alone or add GitHub approvals, a generic bot, an agent-review check, or any combination. Security is enforced via GitHub rulesets that independently require the same checks named in the configuration.

Key Features

Provider-neutral merge queue compatible with Codex, Claude Code, Cursor, and any MCP client
Durable manual deploy gate: user retains final merge decision via a deploy instruction
Authority stored in GitHub labels and authenticated comments, not broad repository roles
Immediate deploy intent recording even during ongoing CI or review
Burst freeze to prevent concurrent merges from causing conflicts
Serial merging of independent work back-to-back
Scaffolds cumulative integration PRs to combine multiple changes
Automatic pause after merge failures to avoid cascading issues
MCP server integration for agent-based queue inspection and operation
Security model leveraging GitHub rulesets as authoritative check identity

Pros & Cons

Pros
  • Keeps final merge authority with the user, not the agent
  • Provider-neutral design works across multiple coding agent platforms
  • Records deploy intent immediately even if checks are still running
  • Pauses merges on failure to prevent broken main branches
  • Open source and free to use with no hidden costs
  • Leverages GitHub's built-in security features (rulesets, labels, comments)
Cons
  • Requires GitHub CLI authentication and careful token permission setup
  • Configuration of checks and policy in .mergequeue.toml can be complex
  • Still relatively early in development (v0.2.25 as of writing)
  • Dependence on GitHub rulesets may add overhead for some teams

Best For

Automating pull request merging in workflows driven by coding agentsCoordinating multiple agent-submitted PRs while keeping human in the loopManaging merge queues for open source projects that use AI coding assistantsEnforcing safe merge policies with manual deploy gates and failure pausing