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
[scanner] review: fetch the linked Linear issue at dispatch and carry it on review.PullRequest #14910
Part of #14906. Builds on #14909 (contract recognition).
Scope (child 2 of 3)
In the dispatch path that builds review.PullRequest, when the contract from #14909 names a Linear issue, fetch it read-only through the existing Linear work source (worksource.LinearSource) and carry the text on PullRequest (for example ScopeContractText). Content: identifier, title, state, description, and the last few comments, byte-capped at about 8–12 KB with a truncation note. Cache per issue updatedAt so a PR with many kicks costs one fetch. Any fetch failure leaves the field empty and must never fail dispatch.
Reviewers stay token-less: the Linear credential is used only by the hub at dispatch, never injected into the ADVISORY tier (linearEnvPairs in src/crux/agent/manager_tokens.go is unchanged).
Tests
A kick for a PR with a fetched issue carries its title and description on PullRequest.
A fetch failure leaves the field empty and the dispatch succeeds.
An unchanged updatedAt serves the second kick from cache with no second fetch.
Text over the cap is truncated with the note.
Why
Reviewers run ADVISORY and cannot read Linear; granting the work-source credential would give them write access. Fetching at dispatch keeps the check deterministic without widening the reviewer tier.
Decision taken by hive: split #14906 along the three steps in its own proposal; this child owns the fetch and cache and is blocked on #14909 for the identifier.
Hi! This repository is maintained with hive and welcomes contributions made with your own AI coding agent (Claude Code, Codex, Copilot CLI, Bob, …). hosted-available-oke-11-placeholder-r05x picked this issue as a good place to start because:
Fork or branch, make the change with your agent, and sign each commit with DCO (git commit -s).
Open a PR whose description says Fixes #14910 — that closing keyword is how hive's contributor lane links the PR to your claim.
Hive runs CI and merges green PRs from claimed contributors automatically.
Paste this to your agent
Fix #14910 in github.com/hivecommons/hive (https://github.com/hivecommons/hive/issues/14910). First open https://hosted-kubestellar-hive-ojv6.hive.hivecommons.dev/contribute?issue=hivecommons%2Fhive%2314910 and claim the issue through the hive relay (sign in with GitHub). Work on a fork/branch; keep the change scoped to the issue; sign every commit with DCO (git commit -s); open a PR whose description contains the line 'Fixes #14910' so the hive's contributor lane can auto-merge it once CI is green. Read and follow https://github.com/hivecommons/hive/blob/HEAD/AGENTS.md before changing code.
Prefer not to drive the loop by hand? Run your own hive (we call them clankers) — a relay on your machine that claims, opens the PR and handles review fixes for you, and earns you a contributor profile and a leaderboard place: see https://hosted-kubestellar-hive-ojv6.hive.hivecommons.dev/contribute.
@hivecommons-hive[bot] this issue was closed by @clubanderson 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
🌱 Good first issue — bring your own coding agent
Hi! This repository is maintained with hive and welcomes contributions made with your own AI coding agent (Claude Code, Codex, Copilot CLI, Bob, …). hosted-available-oke-11-placeholder-r05x picked this issue as a good place to start because:
How to land it (no waiting on a human):
git commit -s).Fixes #14910— that closing keyword is how hive's contributor lane links the PR to your claim.Paste this to your agent
Prefer not to drive the loop by hand? Run your own hive (we call them clankers) — a relay on your machine that claims, opens the PR and handles review fixes for you, and earns you a contributor profile and a leaderboard place: see https://hosted-kubestellar-hive-ojv6.hive.hivecommons.dev/contribute.
If nobody claims it, hive may pick it up itself — claiming first prevents that. Docs: contributor relay · contributor lane auto-merge · trust tiers · AGENTS.md.
🐛 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,…
clubanderson commentedon Oct 28, 2026
Closed: fixed by #15074 (merged).
github-actions commentedon Oct 28, 2026
@hivecommons-hive[bot] this issue was closed by @clubanderson 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.