Skip to content

Branch protection: required context "Hypatia Neurosymbolic Analysis" never matches (blocks all merges) #17

Description

@hyperpolymath

Problem

main branch protection lists Hypatia Neurosymbolic Analysis (bare name) as a
required status check. No check actually reports under that exact name — the Hypatia
workflow reports its check-run as hypatia / Hypatia Neurosymbolic Analysis (job
prefix) and Hypatia. Both pass, but neither matches the required bare context, so
every PR is permanently mergeStateStatus: BLOCKED even when all real checks are green.

Verified on PR #16 (head a2267b5): all 7 required contexts satisfied except
Hypatia Neurosymbolic Analysis, while hypatia / Hypatia Neurosymbolic Analysis :: success
and Hypatia :: success both ran. enforce_admins is false, so only an admin override
can currently land a PR.

Fix (pick one)

  1. Update branch protection — replace the required context
    Hypatia Neurosymbolic Analysis with hypatia / Hypatia Neurosymbolic Analysis
    (the name actually reported), or
  2. Rename the workflow job so the reported check-run name is the bare
    Hypatia Neurosymbolic Analysis.

Option 1 is the smaller change and matches how the governance / * contexts are already
named in the policy.

Impact

Blocks PR #16 (Lean tropical migration — all checks green, commits GPG-verified). Likely
affects every PR to this repo. Estate-wide check: other repos that adopted the same
protection + hypatia wrapper naming may have the identical latent block.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is broken or behaves incorrectlycicdCI/CD: workflows, actions, lockfiles, pins, runners, release gatesgovernancePolicy, rulesets, standards, compliance, and their enforcement

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions