DeployBot은 코딩 에이전트에 대한 공급자 중립 GitHub 병합 큐입니다. Codex, Claude Code, Cursor 또는 MCP 클라이언트를 준비하고 검토 할 수 있습니다 요청; 사용자는 deploy] 라고 최종 합병 결정을 유지한다.

DeployBot은 GitHub 라벨 및 인증된 의견의 권위를 저장합니다. · 레코드는 즉시 배포, 최종 정확한 검토 헤드를 촉진, 동결 파열, 독립적 인 작업 뒤로, 비계 누적 통합 PR, 다음과 같은 main 생산, 실패 후 일시 중지.

설치

v0.2.25] 소스를 GitHub에서 직접 설치:

deploybot init 안전한 스타터 정책을 작성합니다. 이름 * 예제 정책은 각 지원 섹션을 보여줍니다. CLI, MCP, 정책 및 행동 참조 목록 현재 명령, 도구, 옵션 및 구성 필드.

번들 $deploybot] 기술을 사용하여 검사하거나 큐를 작동. 제품 정보 요청은 "배송 파이프라인을 표시,"왜 PR 42 차단?, 과 “이 PR을 배포합니다.” 상태와 진단은 읽기 전용입니다:

Astro 소스 트리의 개발을 위해, 설치 [T5] 대신.

편집 `.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: