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
{{ message }}
Repository navigation
tracker: "Merge failed" chip drawn in the CI / Review column with the raw GitHub error; pending CI captioned "red"; sweep PUTs /merge while required checks are pending #15404
Operator report, hive's own spoke, Activity Monitor, 2026-10-29 11:04 ET. Row hivecommons/docs#496 (closed issue, chips "refs" / "closed") → PR hivecommons/docs#512 "docs: resync the Hive docs mirror from hive@v5".
What the tracker showed
The amber chip "⟳ Merge failed · merge sweep running ⬡" was rendered in the CI / Review column, not Merge gate. Operator: "this is merging from the pr/review column?"
Caption underneath: "Hive: fell back to stage/060-reviewed — Review passed; waiting for merge admission — CI is red (check-pending) 1m ago".
Tooltip: "stage/060-reviewed — hive tried to merge this (automerge sweep) 1m ago and GitHub refused: PUT https://api.github.com/repos/hivecommons/docs/pulls/512/merge: 405 4 of 4 required status checks are expected. []. The lane re-evaluates it on its next pass (next sweep in 7s). Last checked 22s ago. · Next move: hive — approved; a required check is still pending".
Bugs
Column: stageTrackerAnchor maps stage 60 → column 50 unconditionally; the merge-gate chip is drawn on whichever segment is active, so a merge attempt on a 060 row lands in CI / Review. A merge outcome (merging / merge-failed) must always render in Merge gate.
"CI is red (check-pending)": humanizeStageReason renders every check-* / status-* token as "CI is red ()". Pending is not red → "CI running"; failure → "CI failed: "; success → "CI green".
"Merge failed · merge sweep running" is two states at once (the sweep_running branch wins before the merge-failed branch). Retrying → "Merge failed · retrying" with the reason in the tooltip; not retrying → "Merge failed · ".
Raw error in the chip: stageTrackerMergeFailedShort puts the first line of merge_gate.merge_failed into the chip. The chip must be a fixed short phrase; GitHub's text belongs in a Details line of the tooltip, translated to plain words (405 required checks expected → "4 required checks haven't finished"; 405 not mergeable → "branch protection blocks it"; 409 → "branch moved, needs rebase"; 403 → "hive isn't allowed to merge here").
Honest chip: this wasn't a failure — the sweep called PUT /merge before the required checks had reported. "Waiting for CI · 4 checks".
Stage slug leak: "fell back to stage/060-reviewed" / tooltip "stage/060-reviewed — …" expose the lane's slug.
Sweep root cause: when the App cannot read the required-check set the sweep runs server-enforced and lets GitHub decide; GitHub's 405 "N of N required status checks are expected" is recognised (requiredChecksExpectedMergeError) but nothing remembers it, so every pass (event-triggered, "next sweep in 7s") re-PUTs /merge, each refusal recorded as a failed merge attempt that lights "Merge failed" — and burns API quota.
Not a bug: a closed issue whose PR is still open stays on the board (#15267 hides closed superseded PR rows only); the "closed" chip on the issue side is right.
Activity
🐛 tracker: merge outcomes always render in the Merge gate column; pen…