Repository navigation
🐛 dashboard: anchor tracker rows on the open PR when the issue has closed - #14657
Conversation
…osed A PR whose every closing link names a closed issue is still live work. Its row is now the PR's own: closed_issue on the item carries the demoted issue (with GitHub's stateReason so a not-planned close can say so) and the tracker draws the PR's number and title in the lead cell with the closed issue as a muted chip. The PR's stage, modifiers and timestamps are untouched — the issue closing is not a regression. Fixes #14655 Signed-off-by: Andy Anderson <andy@clubanderson.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Open PR overlap checkBase branch: Conflicts are checked with every PR merged onto the current tip of
|
|
@clubanderson is auto-promoted for contributor-lane merging on this PR: the last 5 merged PRs by this author in this hive's repositories have no revert or sentinel-alert evidence. CI, reviewer verdict, diff fences, soak, holds and branch protection still apply. |
|
@clubanderson this PR is held at Failing checks:
Next: the hive does not push to your branch. Push a new head (or reply here); CI and the review swarm re-run automatically and the PR returns to the normal path. |
|
This PR adds three lines to 🐝 Hive Agent: — hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88 |
|
merged by Hive trusted-author auto-merge: author @clubanderson holds role owner and GitHub permission admin on repo; CI green at 9bb6073. |
|
Thank you for your contribution! Your PR has been merged. We'd love to hear how your experience was: share feedback |
….md (#14712) RankActionableIssues gained lines in #14657, so the cited 4676-4686 range no longer covers the AgeMinutes comparison and the docs-citations check on v5 fails with DRIFT. Widen the range to the function's current extent. Signed-off-by: scanner <280983584+hivecommons-hive[bot]@users.noreply.github.com> Co-authored-by: scanner <280983584+hivecommons-hive[bot]@users.noreply.github.com>
Fixes #14655
What
Owner screenshot (2026-10-27 18:15Z): the tracker row for hive#14567 drew the closed issue struck through under a
closedpill as the headline, while its linked PR hive#14568 was still open at 090 awaiting the human's merge click. The row read as stale; it was actionable.A PR whose every closing link (
closingIssuesReferences/Fixes #N) names a closed issue is now anchored on the PR:stage_tracker.go):stageTrackerClosedIssueAnchorsetsclosed_issueon a standalone PR item (not nested, no open/unknown-state closing link, softRefslinks ignored). The PR's stage, modifiers,stage_sinceand timestamps are untouched — the issue closing is not a regression. GitHub'sstateReasonis now read onclosingIssuesReferences(both GraphQL passes) and carried asPRLinkedIssue.StateReason→state_reason, so a not-planned close is distinguishable.index.html): such a row leads with the PR's own icon, author icon,#N titleat full width; the closed issue is a mutedcloses ~~#N~~ · closedchip linking to it;issue closed (not planned)adds a second chip. Sorting, age and Needs attention already keyed off the PR item (090 counts).src/docs/dashboard-sections.mdtracker section gains a Closed issue, open PR note.Tests
TestStageTrackerRowAnchorsOnOpenPRWhenIssueClosed: table over completed / not_planned / PR-merged — row keyed by PR, stage 090 from the PR's record, noregressed, manual-merge gate intact,closed_issuepopulated with state_reason; both closed → no items.TestStageTrackerClosedIssueAnchor: unit table for the anchor rule (nested, open link, unknown state, soft-only, first-closed-wins).