Skip to content

Hypatia PR check (Hypatia) must report on every PR, or be de-required #519

Description

@hyperpolymath

Problem

The bare Hypatia check is a GitHub App check run (distinct /runs/<id> URL), not a workflow job. When it is a required status check (e.g. on affinescript), any PR for which the app does not post a check sits forever at "Expected — Waiting for status to be reported" — a silent merge block.

Evidence

  • Present + green on affinescript#626, affinescript#645, hypatia#517.
  • Absent entirely on gitbot-fleet#307 (no Hypatia check, no hypatia / Hypatia Neurosymbolic Analysis).

So the app posts inconsistently across PRs/bases — exactly the failure mode that blocks merges. Sibling context: hyperpolymath/affinescript#645 (the workflow-side de-gates) and the affinescript pin-reconciliation issue.

Options (pick one)

  1. Always post — have the Hypatia app emit a check run (success, or neutral/skipped when there's nothing to scan) for every PR on repos where it's installed, so the required context is always satisfiable.
  2. De-require it — drop Hypatia from required status checks where it's pinned, and rely on the workflow-emitted hypatia / Hypatia Neurosymbolic Analysis (which the de-gate PRs make unconditional) as the gating signal instead.

Acceptance

  • Decision recorded (always-post vs de-require)
  • On a non-main-base PR, the gating Hypatia signal is either present-and-green or not required — never stuck "Expected"

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions