land-and-deploy

Automating PR merge, CI checks, and production deployment is handled by merging the PR, waiting for CI, and deploying with canary health checks. This ensures safe, audited transitions to production in PR-based release workflows.

A canary deploy health check verifies production health after deploying. The workflow waits for CI to pass, merges the commit, and then monitors the production environment to ensure the release is stable before completing.

Triggering an automated merge and deploy uses natural phrases like "merge", "land", "deploy", or "ship it to production". The workflow takes ownership after the PR is created to auto-merge, await CI, and deploy.

Yes, the automated deploy workflow supports configuration via frontmatter fields like allowed-tools and triggers. This allows you to define how the workflow handles merge commits, CI wait times, and production health verification.

The best way to verify production health after merging a PR is using canary health checks. The workflow automates the merge, waits for CI completion, and then performs canary checks to validate the production environment.

You should avoid automated canary deployment in non-PR-based release workflows. This workflow specifically handles merge commits, CI wait times, and health verification for PR-based release scenarios in software teams.