gstack-land-and-deploy

To automate a merge and deploy workflow with canary checks, you can trigger the process using natural language commands like merge and deploy. The workflow coordinates landing changes, waits for CI, and validates production health via canary verification before completing.

A plan-first gstack preamble is a required safety protocol that executes before routing merge and deploy operations. It enforces plan-mode safety rules and guides the workflow through CI and deploy verification steps until the release sequence finishes successfully.

Yes, you can trigger a ship to production workflow using natural language phrases such as ship to production, land it, or merge and verify. The workflow takes over after intent is detected and creates or updates the PR needed to land and deploy.

To verify production health after deploying a merged PR, the workflow performs canary checks rather than assuming the deploy is correct. This validates production stability automatically as part of the merge-to-deploy sequence.

Yes, the deploy workflow handles CI-aware merge processing by continuing the sequence after merge requests and coordinating the next steps automatically once CI checks are expected to be ready.

Canary verification for release automation relies on executing a plan-first gstack preamble and honoring plan-mode safety rules. It requires guiding through CI and deploy verification steps sequentially until the workflow explicitly completes.