land-and-deploy

Automating GitHub PR merge, CI checks, and deployment requires coordinating CI completion, merge queues, and canary health checks. This process auto-merges a linked PR when checks pass, then verifies production health before completing the release.

Canary health checks during an automated PR deploy monitor production stability after merge, triggering rollback options if issues arise. This verifies deployment health before promoting changes fully, ensuring safe releases without manual handoffs.

You need the gh CLI to automate merging and deploying a GitHub pull request, as it requires access to perform merges and deployments. A linked PR on the current branch and canary health checks are also necessary prerequisites.

You can use auto-merge with CI validation and canary deployment workflows when auto-merge is enabled on your repository. The workflow waits for CI completion, handles conflicts, and coordinates canary production checks before promoting the release.

Automated PR deployment handles merge conflicts and failed CI checks by waiting for CI completion and managing conflict resolution before proceeding. It ensures merges only occur when checks pass, coordinating with canary health checks for safe production promotion.

You should avoid using an automated end-to-end merge and deploy workflow when your repository lacks auto-merge support or when you cannot perform canary health checks. It requires a linked PR and gh CLI access to function reliably.