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

depended on by

Claimed units

  • extends
    {
      "nature": "additive",
      "spec": "002-environment-lifecycle",
      "unit": {
        "kind": "directory",
        "path": "crates/statecraft-home/"
      }
    }

Source headings

  1. 067: A post-merge push runs only the cache saves and the gate
  2. 1. Purpose
  3. 2. Territory
  4. 3. Behavior
  5. 3.1 What a post-merge push runs
  6. 3.2 The cache steps
  7. 3.3 ci-gate's post-merge rule
  8. 3.4 Called workflows
  9. 3.5 Without a required queue
  10. 3.6 The revision
  11. 4. Out of scope
  12. 5. Resolved decisions
  13. Verification

Frozen anchors

No frozen anchors declared.