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
[reviewer] Review backlog (correctness): Docs say sweep runs after every CI enrichment pass; it is skipped in API-budget conserve mode #16695
Blocked on PR #16681. This finding came from reviewing PR #16681 and is about code that PR is changing. Fix it in the PR, or leave it: when the PR merges the hive checks whether the finding is still on the base branch — closing this item as completed if its file or symbol is gone, lifting the block otherwise — and unblocks this item for re-triage if the PR is closed without merging. Once it is unblocked, check the finding still applies on the base branch; if it is already fixed, close this item without a PR.
Filed from an out-of-scope finding in the Hive review of PR #16681.
PR: #16681 (#16681)
Perspective: correctness
Severity: info (P3)
Finding: Docs say sweep runs after every CI enrichment pass; it is skipped in API-budget conserve mode
Evidence: src/docs/operator-reference/runtime-and-quota.md:265
- **Gated workflow runs are approved for trusted heads.** After each CI
src/docs/operator-reference/runtime-and-quota.md:265 and src/docs/webhooks.md:118 state the approval sweep runs after each CI enrichment pass, but src/cmd/hive/main_eval_cycle.go:584-586 only calls SweepWorkflowApprovals when !budgetDecision.SkipOptional. Under budget conserve mode gated heads wait until the next non-skipped cycle. Advisory wording precision only; no behavioural defect.
Unblocked: source PR #16681 closed unmerged — re-triage against current base. A superseding PR often lands the same lines, so the finding may still apply; close this item only if it no longer does.
🔒 Claimed by agent scanner (agent on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 2h0m0s without activity and renews while the work continues. Reply /unclaim to release, or /claim to take it over if you outrank the holder.
Claim history
2026-11-05 08:39 UTC — claimed by scanner (agent on hive hosted-available-oke-11-placeholder-r05x)
@hivecommons-hive[bot] this issue was closed by @kubestellar-prow[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.
Activity
hivecommons-hive commentedon Nov 5, 2026
Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor.
Unblocked: #16681 is no longer open. This issue is actionable again.
hivecommons-hive commentedon Nov 5, 2026
Unblocked: source PR #16681 closed unmerged — re-triage against current base. A superseding PR often lands the same lines, so the finding may still apply; close this item only if it no longer does.
hivecommons-hive commentedon Nov 5, 2026
🔒 Claimed by agent
scanner(agent on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 2h0m0s without activity and renews while the work continues. Reply/unclaimto release, or/claimto take it over if you outrank the holder.Claim history
scanner(agent on hive hosted-available-oke-11-placeholder-r05x)hivecommons-hive commentedon Nov 5, 2026
Fixed by #16736 (merged 6ed3e5e). Closing. Reply /reopen if the problem persists.
github-actions commentedon Nov 5, 2026
@hivecommons-hive[bot] this issue was closed by @kubestellar-prow[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.