You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Parent: Branch Enforcement (#703). Phase 2 of 2. Prerequisite: Advisory Guard (#704) proven quiet + lane-list ratified by Logan.
Goal
Promote the advisory check to a required status check, so any PR whose head → base violates the ratified lane schema is blocked from merging.
Queue-safety (decide before flipping to required)
The merge queue re-runs required checks in the merge_group context. Decide whether the guard gates at PR-entry (on: pull_request) or in-queue (on: merge_group) — they gate at different moments, and a check that only runs on pull_request will not re-run for the queue.
Always exempt gh-readonly-queue/** (the queue's own internal branches), or the queue dead-locks on itself.
Roll out only after the Advisory Guard window is quiet, so the required check does not light up against legacy drift and stall the 55-PR backlog further.
Scope boundary (explicit, so this isn't oversold)
This enforces the branch-name schema only — it is identity-independent. It does not, and cannot, enforce authority/approval gates (CODEOWNERS, "human approval," reviewer-≠-author): those remain convention, not control, until agent identity separation lands (see #398). Keeping that boundary explicit prevents this from being mistaken for a trust gate it cannot be.
Activity