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
Activity Monitor: Fixing pill without actor icon on bot PRs, PR drawn twice under two issues, Merged-today counter far from the gate #15071
1. "Fixing" pill with no actor icon, and nobody is fixing
hivecommons/docs#500 ("docs: resync the Hive docs mirror from hive@v5", opened by github-actions[bot], linked issue docs#496 closed, CONFLICTING, superseded by merged #497) shows Fixing with no actor icon, while hive rows (e.g. hive#14921) show Fixing ⬡. The SPA picks the icon from author_kind, which is empty for a bot login, and the 070 lane is just a classification: no agent, author or clanker is working on #500; the hive does not fix bot PRs, it waits for the bot's next nightly run.
Wanted: for every stage pill with an actor: hive → ⬡ honeycomb, contributor clanker → robot icon, human → person glyph (same as Needs human decision), unknown / nobody actively working → no icon and a tooltip "no one is working on this right now — ". The actor must come from a server-derived payload field stage_actor: {kind: hive|clanker|human|bot|none, login, since, why}, never from heuristics on login strings in the SPA. When nobody is working on it the pill must not read as an active Fixing; say the state in plain words (e.g. "Conflicting · bot PR") with the PR author's icon (bot).
2. hive#14921 drawn twice
PR #14921 appears as two identical "↳ #14921 … Fixing ⬡" rows. Root cause: its body says Closes #14906 (closed), Closes #14910, Closes #14911; both #14910 and #14911 are open and listed, each lists the PR once in linked_prs, and each issue row renders the PR as its single covering PR. The per-issue dedupe in Go never saw a cross-issue duplicate. Wanted: one drawn row per PR (payload-level drawn_under), the other issue(s) point at it, with a fixture reproducing it.
3. Merged-today counter placement
PR #15014 added the "Merged today: N" chip and the hex token that lifts from the ✓ cell to it, but the chip lives in the filter chip bar. Wanted: directly above the Merge gate / ✓ column header (right-aligned over the gate), kept visible when the filter bar wraps; the token flight targets the new location; ⚙ → Merges → Celebrate merges and reduced-motion handling unchanged; a node fixture test that the counter element lives in the header region and the celebration target id resolves.
🔒 Claimed by @thatguywob (contributor on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 30m0s without activity and renews while the work continues. Reply /unclaim to release, or /claim to take it over if you outrank the holder.
@clubanderson this issue was closed by @hivecommons-hive[bot] as completed.
If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.
If you are still seeing the problem, comment /reopen and it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.
Activity
hivecommons-hive commentedon Oct 28, 2026
🔒 Claimed by @thatguywob (contributor on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 30m0s without activity and renews while the work continues. Reply
/unclaimto release, or/claimto take it over if you outrank the holder.hivecommons-hive commentedon Oct 28, 2026
🔓 Claim by @thatguywob released (lease revoked).
🐛 Activity Monitor: server-derived stage actor icons, one row per PR,…
🐛 Activity Monitor: server-derived stage actor icons, one row per PR,…
🐛 Activity Monitor: server-derived stage actor icons, one row per PR,…
github-actions commentedon Oct 28, 2026
@clubanderson this issue was closed by @hivecommons-hive[bot] as completed.
If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.
If you are still seeing the problem, comment
/reopenand it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.