ci(required-contexts): add E2E Peer Visibility to allowlist SSOT (#1296) #2733
Reference in New Issue
Block a user
Delete Branch "ci/required-contexts-add-peervis"
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?
One-line allowlist SSOT sync (#1296 flip follow-through)
Branch protection on
mainwas flipped to requireE2E Peer Visibility (literal MCP list_peers) / E2E Peer Visibility (pull_request)(the #1296 flip, after #2704 made the gate required-ready).lint_no_coe_on_requiredlive-cross-checks.gitea/required-contexts.txtagainstbranch_protections/mainand was failing on the drift (BP has 4 contexts, the allowlist had 3). This adds the 4th to the SSOT.This un-reds
main—lint-no-coe-on-required (push)is currently red on main HEAD because of this drift. The SSOT guard postdates the #1296 checklist (fileVerified 2026-06-10), which is why it wasn't in the original step list.Refs #1296.
🤖 Generated with Claude Code
APPROVED on head
2b8bf1bf.Fast 5-axis review: the diff is exactly the required SSOT sync for #2732. It adds
E2E Peer Visibility (literal MCP list_peers) / E2E Peer Visibilityto.gitea/required-contexts.txt, does not add the non-required(local)variant, and changes no other file. This matches the live BP-required context andlint-no-coe-on-requiredis green on this head, so it fully covers the main-red #2732 drift. No security/performance/readability concern in this one-line CI allowlist update. CI / all-required is green. /sop-ack/sop-ack