Skip to content

Activity Monitor: Let hive decide / row actions are all-or-nothing on an issue with two nested PRs (#15017 + #15020 under #15009) #15055

Closed

Description

@clubanderson

What the owner saw (2026-10-28 14:19 ET, Activity Monitor screenshot)

Issue row hive#15009 carries two nested PRs: #15017 Ready for human merge · untrusted author and #15020 Needs human decision + hold.

I don't see a way to "Let hive decide" for one or more of the PRs. It's currently all or nothing.

Why

The ⋯ context menu, Let hive decide and Approve live on the issue row and act on "its nested PR" (stageTrackerDecisionTarget returns the first parked linked PR). With two or more PRs that is ambiguous: the menu decides one PR without saying which, the delegated decision (POST …/items/{issue}/decide-delegated, type: "issue") picks one silently, and the sub-rows have no gutter of their own — no checkbox, no ⋯ — so a PR cannot be selected or acted on by itself.

Expected

  1. Every nested PR sub-row has its own ⋯ menu (and the needs-human popover opened from its chevron acts on that PR): Let hive decide, Approve, Close as superseded (pre-filled with the sibling when there are exactly two), Won't fix, Give direction, Hold/Release. runRowAction(action, row) receives the PR row object (number, repo, head), not the parent. The issue row keeps issue-scoped actions and, with ≥2 nested PRs, an explicit Let hive decide — all N PRs.
  2. Sub-rows are selectable; the selection bar offers Let hive decide (N selected), one job per item, one tally toast ("3 sent · 2 decided · 1 no-op"), honouring the per-action confirm/skip of ✨ Activity Monitor: live row feedback — confirm opt-out, result toasts, working cue, event line, merge celebration #15014.
  3. A delegated decision on an issue with ≥2 open PRs must not pick one: the job lists each PR's outcome and the toast shows them.

Builds on #14995 (needs-human popover, decision_needed.options, runRowAction), #15014 (row-action toasts, confirm skipping, tracker-cues), #15013, #15011, #15016 (adoption); stays additive to #14992.

Activity

  1. github-actions commented on Oct 28, 2026

    @github-actions
    Contributor

    @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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions