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: secondary issue of a shared PR shows soaking in PR-in-progress lane instead of Merge queue #17324
Seen on hive's hive at 573eb03 (2026-11-09 01:09Z). PR #17308 closes two issues, #17292 (primary) and #17302 (secondary — its row shows the compact "↳ #17308 · under #17292" chip instead of the PR title). The PR is in its merge-queue soak.
Why: stageTrackerLinkedSorted drops PRs whose drawn_under names another row, so the secondary row falls back to the issue's own stage (030/040 → PR-in-progress lane) while stageTrackerCoveringPR still overlays the PR's merge-gate word. The lane and the word come from different sources.
Expected: a secondary issue that shares a PR renders the PR's stage in the same lane as the primary — the stage position is a property of the PR, not of the issue's role. The secondary row keeps its compact "#PR · under #primary" chip and does not redraw the PR in the PR column.
Activity
hivecommons-hive commentedon Nov 9, 2026
🔓 Claim by agent
scannerreleased (holding agent relaunched).Claim history
scanner(agent on hive hosted-available-oke-11-placeholder-r05x)scanner(agent; holding agent relaunched)hivecommons-hive commentedon Nov 9, 2026
/unclaim
Scanner stood down: #17325 by the maintainer already fixes this; the redundant
scanner/fix-17324branch was deleted unopened.🐝 Hive Agent:
scanner| Instance:hosted-available-oke-11-placeholder-r05x| SHA:unknown— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88
🐛 Activity Monitor: secondary issue of a shared PR rides the PR's lane (