land-and-deploy

Automate the release workflow from PR merge to production deployment with health checks.

Updated Dec 13, 2017

Search Tags:#automation #deployment #release #ci #canary #pr-merge #land-and-deploy

Ready to run

npx skills add https://github.com/dogeared/tnra --skill land-and-deploy-dogeared

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/dogeared/tnra/tree/main/.claude/skills/gstack/land-and-deploy
Command: npx skills add https://github.com/dogeared/tnra --skill land-and-deploy-dogeared

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land-and-deploy automates the end-to-end release workflow from PR merge to production deployment, reducing manual handoffs and the risk of failed releases.

Core Features & Use Cases

Automates the merge-to-deploy sequence: merge PR, wait for CI, trigger deploy, and perform production health checks.
Supports common release journeys: merge, land, deploy, ship, and verification.
Works with existing CI/CD setups and can be extended with scripts and references.

Quick Start

Run land-and-deploy to merge the PR, wait for CI, deploy to production, and verify canary health.

Frequently Asked Questions about land-and-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate the PR merge to production deployment workflow?▼

Automating the PR merge to production deployment workflow involves enforcing a deterministic sequence that merges feature branches, waits for CI, triggers the deploy, and runs production health checks. This reduces manual handoffs and failed release risks.

What is canary verification in a release pipeline?▼

Canary verification in a release pipeline is a post-deploy health check step that validates production stability after shipping. It ensures the deployed code performs safely before the automated release sequence completes.

How can I ensure safe production deployments after merging code?▼

Safe production deployments after merging code require a deterministic sequence that waits for CI completion and performs canary verification. This automated workflow verifies production health immediately after shipping.

Does this deployment automation work with my existing CI/CD pipelines?▼

This deployment automation integrates with existing CI/CD pipelines and supports common release journeys like merge, land, deploy, and ship. It can be extended with scripts and references to fit your current setup.

What are the limitations of automating release workflows with a deterministic sequence?▼

Automating release workflows with a deterministic sequence is limited to teams that merge feature branches, wait for CI, ship to production, and require post-deploy health checks. It does not support workflows outside this specific end-to-end release journey.

What is the best way to handle merge, land, deploy, and ship sequences?▼

Handling merge, land, deploy, and ship sequences is best accomplished by automating the end-to-end release workflow. This enforces a deterministic sequence that integrates with CI/CD pipelines and verifies canary health.