ci-pipelines · git:20261107.275a27d · 2026-11-07 · sha256 bdf3af26e304b70d
ci-pipelines git:20261107.275a27dA
Immutable. This exact content never changes and is served at /api/v1/blob/bdf3af26e304b70d.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_oecjdqcxdudzwz3n/bdf3af26e304b70d92d4e4cad7b5cb19ed20630ff75c09864e495c8812d8cfc7.json
Then /plugin install ci-pipelines@markdownregistry-oecjdqcxdudzwz3n in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: ci-pipelines description: Use when changing continuous integration, GitHub Actions workflows, runners, caches, or deployment pipelines. --- # CI pipelines CI fails closed. A step that can't establish what it relies on, such as a diff, a signature, or a gate result, takes the full path or fails the run. Reference external actions by their major-version tag, such as `actions/checkout@v7`, not by commit SHA. The owner accepts the risk that a tag is retargeted, so don't propose SHA pins. Each job bills at least one minute, so fold sub-minute checks into an existing job that runs at the same trust level. ## GitHub behavior A workflow-level `paths` filter can't prove that a gate has nothing to check, because GitHub evaluates it against a bounded list of changed files. Classify the checked-out diff in a job instead. GitHub counts a skipped job as a passing required check. On runs that skip a gate, the job that reports its required check needs another name. ## Caches Save caches only from successful default-branch runs. Other runs only restore them. Leave package and browser stores at their tools' default paths. Turbo's strict environment hides the variables that relocate a store from the tools a task spawns. Never cache image layers with `type=gha`, because their churn in the shared Actions cache quota costs more than the cache saves. Cache them in the image's registry instead, as `type=registry,ref=ghcr.io/<owner>/<image>:buildcache`. Every build reads it, and only default-branch push builds write it, with `mode=max,image-manifest=true,oci-mediatypes=true`. Registry retention must keep the `:buildcache` tag. ## Deployment Deploy a commit only after the quality gate passed for that exact commit. Serialize deployments with FIFO queueing (`concurrency.queue: max`), because otherwise a late run for an older commit can evict the pending run for the newest one. The gate loads an app's production build in a browser and fails on an uncaught page error, because a server-only module in the browser bundle can leave every page unresponsive while every test passes. Before a release, the job that builds the app's image starts the container, waits for its health check, sends SIGTERM, and fails unless the app exits as the [app-release contract](../declarative-infra/references/app-release.md) requires, because a shell or runtime running as PID 1 can ignore the signal.