land-and-deploy

Automating PR merge and production deployment after CI passes is done by triggering a land-and-deploy workflow. This process handles pre-flight checks, waits for CI, merges the PR, and then triggers production deployment automatically.

Yes, you can verify production health using canary checks after a GitHub PR merge. The workflow validates deployment strategy and performs canary health checks, automatically offering a safe rollback if production issues are detected.

Automated rollback during a failed production deployment works by detecting issues during canary health verification. If canaries detect anomalies after the PR merge and deployment, the workflow initiates a safe rollback to restore the previous stable state.

Yes, you need GitHub CLI to enforce pre-merge guardrails for CI deployment. The workflow relies on GitHub CLI to perform pre-flight checks, handle merge conflict detection, and manage the PR merge process safely before triggering production deployment.

Yes, you can configure platform-aware deployment verification for your specific environment. The workflow allows you to define deployment verification parameters and platform-specific settings within a CLAUDE.md configuration file to ensure accurate canary checks.