Skip to content

policy: estate settings standard β€” merge opts, protection, required-checks = πŸ”΄ Gate set (WS4)Β #408

Description

@hyperpolymath

Goal

Define the canonical GitHub settings every repo should converge to, and realign the stale required-check contexts that deadlock PRs estate-wide.

Do

  • Specify: merge-button options, branch-protection shape, feature toggles, and the required status checks = the πŸ”΄ Gate tier (see CI-CRITICALITY promotion issue).
  • Realign stale required contexts: the governance / * group is stale on ~190 repos (renamed/regrouped β†’ context no longer matches emitted name). Define the rename mapping.
  • Confirm true deadlocks via the farm ci-deadlock-audit union signal before writes. Branch-protection writes are owner-gated.

Context

WS2 audit: 336/373 protected, 234 with required checks, 102 toothless. Report in dev-notes/estate-settings-audit-2026-06-22/. Execution/automation tracked in reposystem.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions