GitHub, CI & Auto-Merge
Push access, auto-merge after green CI, and visibility into PRs and pipelines.
Introduced at Warp 2. Connecting GitHub and letting CI be the merge gate is what frees the agent from babysitting pipelines: it opens a PR, enables auto-merge, and the PR merges itself once required checks are green. Same machinery doubles as the deploy gate.
GitHub connected
The agent needs GitHub connected and the ability to push — the entry point for everything else here.
Auto-merge after CI passes
Enable auto-merge after CI passes so agents don't poll CI manually. They open a PR, enable auto-merge, and the PR merges itself once required checks are green — no waiting loop, no manual re-checks.
PR & pipeline visibility
Give the agent credentials to check PR status and CI/CD pipelines, so it can tell when a check failed, why a merge is blocked, and whether a deploy went out.
CI as both merge gate and deploy mechanism
Production deploys themselves should run through GitHub Actions (see Credentials & the Safety Spine), not from the agent's hands. CI is both the merge gate and the deploy mechanism— the agent triggers work, but the keys to production stay in Actions where they're deterministic and auditable.
main behind a green CI run but production deploys still go through Actions, the blast radius stays contained — that's the Warp 2 contract.