land-and-deploy

Automating GitHub PR merge and production deployment involves detecting the PR, merging it, waiting for CI, and running canary health checks. This workflow coordinates the end-to-end process to verify deployment readiness and minimize production risk.

The ship-then-land pattern is a release engineering workflow where code is staged before final merge and deployment. This Skill automates this pattern by handling PR detection, CI validation, and canary-based health checks before safely landing changes in production.

To run canary health checks before a full production release, you need safety gates that validate deployment patterns across platforms. This workflow detects deployment patterns, executes canary checks, and provides safe-revert options to ensure production health.

Yes, this deployment automation works with your current GitHub branch by automatically detecting the associated PR. You can also specify an explicit PR URL or number if you need to target a specific pull request for the land-and-deploy workflow.

Yes, you can automatically revert a failed production deployment because the workflow includes safety gates and safe-revert options. If canary health checks fail or production issues are detected, the system coordinates a rollback to minimize risk.