Production Release Gating

Stop every push/merge to main from shipping to production — deploy only on a real release. Use when a merge to main unexpectedly deploys to prod, when you want production to deploy only on a semantic-release version (not every commit), when setting up preview-on-feature-branch but gated-prod-on-main, wiring a Vercel Ignored Build Step / `ignoreCommand`, promoting to a staging/`production` branch, or triggering a deploy from a published GitHub Release (GKE, self-hosted, dispatchable targets). Covers three named patterns — Release-Triggered Deploy (`on: release`, `types: [published]`), Promotion Branch (staging/`production`, most portable), and Build-Skip Gate (the Vercel `ignoreCommand` script) — when to use which, works with both per-merge and pooled releases, branch-aware previews, and monorepo dependency-release handling.

wiiiimm Updated
glassOS — a desktop made of glass-gl surfaces: menu bar, dock, and draggable app windows (including the Spotify Music and YouTube Video apps) refracting a flora

File contents

wiiiimm/glass-gl commit 1ab5d506e7

Frequently asked questions

npx get-skill add wiiiimm/production-release-gating