land-and-deploy

To automate GitHub PR merge, deployment, and production health verification, use an automated release workflow that merges ready pull requests, waits for CI and deploy completion, and runs canary checks to validate post-deploy health.

Canary verification in a deployment workflow is a post-merge strategy that monitors production health after a deploy. It validates the new release and can trigger a revert if production health issues are detected during the canary checks.

Pre-merge checks to prevent broken pull requests from deploying include validating CI status, detecting merge conflicts, analyzing test results, and checking review staleness and PR body documentation accuracy before proceeding with the merge.

Yes, the merge and deploy process supports merge-queue polling on GitHub. It merges the release pull request efficiently, handles merge-queue polling when applicable, and captures timing and merge details for the deployment workflow.

Yes, you need GitHub CLI authentication to automate merging and canary verification. The release engineering workflow requires it to validate pull request and CI states, check conflicts, and execute the merge on GitHub.