land-and-deploy

Automating PR merge, CI checks, and production deploy is achieved by providing a PR URL or branch to trigger a hands-off release. The workflow merges the PR, waits for CI to pass, deploys to production, and validates canary health automatically.

Canary verification in an automated deployment pipeline validates production health after a release. It checks the canary deployment to ensure stability, maintaining rollback readiness and allowing operator intervention through configurable prompts.

To start an automated post-merge release process, provide a validated PR URL or branch name. This triggers the workflow to automatically merge, wait for CI, deploy to production, and verify production health.

Yes, automated deployment works with GitHub PRs and CI pipelines. This workflow is designed for projects using GitHub PRs and CI, automating the end-to-end post-merge workflow including merge, deployment, and canary checks.

Yes, you can configure operator intervention prompts during production deployment. The workflow supports rollback readiness and uses configurable prompts via AskUserQuestion to enable manual oversight during the release process.

If CI fails after an automated PR merge, the workflow halts before deploying to production. It waits for CI to pass as part of the post-merge workflow, ensuring only validated PRs trigger the deployment pipeline and canary checks.