067-post-merge-push
Setup profile revision 24: where the merge queue is required, a push to the default branch runs only the cache saves and ci-gate
Lifecycle approvedImplementation completeVerification unknownQualification unknown
Amends specs 002, 032, 044 and 058. Where the policy records a required merge queue, the queue has already judged the exact commit a push to the default branch carries. github-actions-rust revision 24 skips every job that judges on that push, keeps the cache steps, and has ci-gate admit the skips by an explicit post-merge rule only when the pushed commit passed ci-gate in its merge-queue run. Repo-owned called workflows receive a boolean post_merge input. Without a required queue nothing changes.
Read the full pinned specification ↗Relationships
depends on
depended on by
Claimed units
- extends
{ "nature": "additive", "spec": "002-environment-lifecycle", "unit": { "kind": "directory", "path": "crates/statecraft-home/" } }
Source headings
- 067: A post-merge push runs only the cache saves and the gate
- 1. Purpose
- 2. Territory
- 3. Behavior
- 3.1 What a post-merge push runs
- 3.2 The cache steps
- 3.3 ci-gate's post-merge rule
- 3.4 Called workflows
- 3.5 Without a required queue
- 3.6 The revision
- 4. Out of scope
- 5. Resolved decisions
- Verification
Frozen anchors
No frozen anchors declared.