Repository navigation
Description
Target: v6.
Target branch:
v6only. Open the PR with--base v6.hive-open-prdefaults to the repo's default branch (v5) when--baseis omitted.
Citations:path:lineagainstv6@7f89f9d01, paths relative tosrc/.
When a contributor's agent reports "blocked on #N", record that dependency so the hive lifts blocked itself once #N closes.
Background
A contributor relay applies blocked on a blocked verdict (markIssueBlocked → markIssueLabel, bin/contributor-relay.js ~8068-8134). It writes no marker and names no blocker the hive can read, so the only ways off blocked today are human: the #12376 park and /hive approve, per the #7924 decision. Meanwhile the dependency the agent found is lost. projectbluefin/testsuite#975 is blocked on the open issue server#450. Eight agents re-discovered that and re-posted it between 10-11 and 10-27.
A companion PR stops the hive lifting such relay-applied blocks every few minutes: #15022. This issue is the second half. When the verdict names its blocker, record it in a form the hive already lifts on close.
What exists
-
Native GitHub "blocked by" dependencies (✨ issues: when an agent splits an issue, record the order as GitHub "blocked by" links and keep blocked children out of the kick list #9839 / 🐛 hard-suppress reconcile never lifts hive-applied
blockedwhen the native "blocked by" dependency closes #12522):Client.AddBlockedBy(pkg/github/issue_dependencies.go:301, takes the blocker's databaseid);fetchBlockedBy(:149);ReconcileHiveHardSuppress(pkg/github/hard_suppress_reconcile.go:71; lines 29-31 describe it) liftsblockedwhen every native blocker of the issue is closed.
The dashboard and contributor admission (
dependency_blocked) read the same links. -
The PR marker
<!-- hive:blocked-on pr=owner/repo#N -->(pkg/github/issue_blocked.go:57-93), lifted when that PR merges or closes. -
The relay's blocked verdict reaches the hub in
pkg/dashboard/contribute_ws.goaround:4479, wherereclassifyToolingBlockedVerdictalready readsverdictReason.
Change
- Parse the blocker. After the tooling reclassification at
contribute_ws.go:4479, when the verdict is stillblocked, parseverdictReasonfor one blocker reference:owner/repo#N,#N(the task's repo) or a GitHub issue or PR URL. If there are several, take the first. - Resolve it with one
Issues.Get(the App token, the hub's normal REST caller):- An open issue: call
AddBlockedBy(taskRepo, taskIssue, blocker.GetID()). The existingReconcileHiveHardSuppresspath then liftsblockedwhen it closes, and the dashboard shows the dependency. - An open PR: post the existing
BlockedOnMarker(repo, pr)comment on the blocked issue. It is lifted on merge or close. - Already closed, or the read fails: record nothing and log it. The block stays human-lifted, as today.
- An open issue: call
- Idempotence: do not add a native link or marker that already exists. Check
fetchBlockedBy/ the marker first, and dedupe per task. - Do this off the websocket handler goroutine, as
releaseToolingBlockedIssueis. - Optional: let the sweep read
<!-- hive:recheck-after … -->from comments as well as the issue body (blockedRecheck,issue_blocked.go:129). A relay could then set a deadline for an external blocker (a hosted run, an upstream release) without editing the issue body.
Acceptance criteria
- A blocked verdict whose reason names an open issue in the same or another repo leaves a native "blocked by" link on the task issue.
blockedstays until that issue closes and is then lifted by the existing reconcile, with no re-offer and no new agent comment in between. - A reason that names an open PR leaves a
hive:blocked-on pr=marker, which is lifted on merge or close. - A reason with no resolvable reference behaves exactly as today.
- No duplicate links or markers are created on a re-delivered verdict.
Test plan
- Parsing: a table test for the blocker-reference parser:
owner/repo#N,#N, an issue URL, a PR URL, prose with no reference, and two references (the first wins). - Hub tests next to
pkg/dashboard/contribute_ws_blocked_verdict_test.goandcontribute_blocked_tooling_test.go:- with a fake GitHub returning an open issue,
AddBlockedByis called once with the blocker'sid; - with an open PR, the marker comment is posted;
- with a closed target or a 404, nothing is written;
- on re-delivery, nothing is written twice;
- a tooling-reclassified verdict writes nothing.
- with a fake GitHub returning an open issue,
- End-to-end: an existing
ReconcileHiveHardSuppresstest, or a new one, shows a native blocker closing lifts the relay'sblocked. - Unknown, check before shipping: whether
AddBlockedByaccepts a blocker in another repo (testsuite#975 is blocked on server#450). If GitHub refuses, fall back to a marker form for issues,issue=owner/repo#Nin theissue_blocked.gogrammar, lifted on close.
Out of scope
- Re-checking an existing blocker note when the blocker moves (the 🐛 fix(park): re-check 045 parks when the work they wait on moves; /hive approve needs a recommendation #14309 park re-check pattern, which excludes
blockedtoday atpkg/github/issue_park_recheck.go:186-188). - Changing who may lift a relay block with no named target (🐛 bug(contribute): a no_work_needed that names an external blocker is re-offered on the 4h backoff and the finding is thrown away — let the verdict say 'blocked' and hold for the full cooldown / apply the existing 'blocked' label (utah#100) #7924 / 🐛 [v6] your-turn: an issue labelled
blockedon a person never reaches the inbox and gets no reply menu #12376).
Activity
hivecommons-hive commentedon Oct 28, 2026
🔒 Claimed by @Karibhou (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.✨ feat(contribute): record the blocker a relay's blocked verdict names
hivecommons-hive commentedon Oct 28, 2026
🔓 Claim by @Karibhou released (lease revoked).
✨ feat(contribute): record the blocker a relay's blocked verdict names
✨ feat(contribute): record the blocker a relay's blocked verdict names (
hivecommons-hive commentedon Oct 28, 2026
Fixed by #15123 (merged ea6e470). Closing. Reply /reopen if the problem persists.
github-actions commentedon Oct 28, 2026
@Danathar 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.