DeployBot 是一个与提供者无关的 GitHub 代码代理合并队列。 Codex、Claude Code、Cursor 或任何 MCP 客户端都可以准备并审核拉取 请求;用户通过说 deploy 保留最终合并决策。

DeployBot 将权限存储在 GitHub 标签和认证评论中。它 记录立即部署意图，促进最终精确审查的头部， 冻结爆发，连续合并独立作品，搭建脚手架 集成PR，跟踪main完成生产过程，失败后暂停。

安装

直接从 GitHub 安装经过审核的 v0.2.25 源代码提交：

deploybot init 编写安全启动策略。注释 示例政策显示所有支持的部分， CLI、MCP、策略和动作引用列出了所有 当前命令、工具、选项和配置字段。

调用捆绑的$deploybot技能来检查或操作队列。典型 请求内容包括“展示交付流程”、“为什么PR 42被阻挡？”， “部署此PR。”状态和诊断为只读：

如需从Astro源代码树开发，请安装 ./packages/agent-merge-queue[mcp] 反而是这样。

编辑 '.mergequeue。

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.

Install

Install the reviewed v0.2.25 source commit directly from GitHub:

python3 -m pip install \
  'deploybot-merge-queue[mcp] @ git+https://github.com/Forward-Future/DeployBot.git@3fb42e2e3cf3a6f21cddf43e3d06deaa24a3ac80'
deploybot init

deploybot init writes the safe starter policy. The annotated example policy shows every supported section, and the CLI, MCP, policy, and Action reference lists every current command, tool, option, and configuration field.

Invoke the bundled $deploybot skill to inspect or operate the queue. Typical requests include “show the delivery pipeline,” “why is PR 42 blocked?”, and “deploy this PR.” Status and diagnostics are read-only:

deploybot status
deploybot status --json
deploybot doctor
deploybot metrics --json
deploybot inspect 42 --json

For development from the Astro source tree, install ./packages/agent-merge-queue[mcp] instead.

Edit .mergequeue.toml to name the required checks, optional review providers, and every exact GitHub login whose queue markers are trusted. Do not grant authority by broad repository role. GitHub verifies comment authors; its normal token permissions control label, comment, and merge writes. Authentication comes from the GitHub CLI:

gh auth login
deploybot ensure-labels
deploybot doctor

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 model

Protect the base branch with a GitHub ruleset that independently requires the same checks named in .mergequeue.toml, and do not give DeployBot’s merge credential permission to bypass that ruleset. DeployBot reads check display names to coordinate the queue; GitHub’s ruleset is the authoritative check identity and the final atomic merge guard.

Keep workflow changes reviewed, pin third-party Actions to full commit hashes, and never execute pull-request-head code in the privileged coordinator. The MCP server uses the local process’s existing GitHub credentials and accepts explicit repository selectors, so run it only from a trusted coding client and workspace.

Durable manual deploy gate

The installed agent adapter treats the user’s exact deploy instruction as authority for that thread’s PR only. It records the intent immediately—even if CI or review is still running: