governance: require sop-checklist all-items-acked (MERGE LAST + owner BP flip) #3186
Reference in New Issue
Block a user
Delete Branch "governance/require-sop-checklist-all-items-acked"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds
sop-checklist / all-items-ackedto the merge-blocking required-contexts list, so the review checklist (#3184 items #8 scope-matches + #9 public-repo-hygiene) becomes mandatory — reviewers must/sop-ackeach one.MERGE LAST. Land only after the in-flight batch (#3183 security delete, #3184 items, #3185 RFC) merges and after #3184 lands items 8/9 — otherwise every open PR fail-closes on un-acked items.
Owner step (hard enforcement): required-contexts.txt alone did NOT hard-block on #3181 (E2E-Concierge-Creates-Workspace is in the file but merged red because it's not in BP). To hard-enforce, the owner adds
sop-checklist / all-items-acked (pull_request)to molecule-core branch-protection status_check_contexts. This PR is the documented-list companion to that BP flip.APPROVED: #3186 is a one-line governance change adding
sop-checklist / all-items-ackedto .gitea/required-contexts.txt. This matches the intended merge-lane hardening now that #3196 fixed the stale 7-vs-9 SOP checklist test expectations. No production code or secrets touched; performance impact is nil. The “MERGE LAST” note still matters operationally, but the current head is acceptable from a code-review standpoint.