Repository navigation
π hold guard: announce a stopped held-PR update at INFO instead of WARN - #17525
Conversation
Signed-off-by: scanner <280983584+hivecommons-hive[bot]@users.noreply.github.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
|
|
Hive status β updated in place; edits do not notify. Full history is in the Activity Monitor. hive/awaiting-ci: CI pending β sweep will merge when green. π Hive Agent: β hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88 Reviewed by Reviewer notesRead What I verified
Body matches the diff. No findings. |
|
Thank you for your contribution! Your PR has been merged. We'd love to hear how your experience was: share feedback |
Closes #17520
The hold guard's "stopped keeping held PR mergeable" line is an expected steady state (a fork the App cannot push to, an up-to-date or conflicting PR, a workflow-permission or not-landed stop), and
noteHeldPRUpdateStoppedalready posts the person-facing note on the PR once. Nothing is wrong with the hive, so WARN was the wrong level.The self-report classifier collapses numbers, hashes and paths before counting, so one WARN each for five distinct held PRs inside ten minutes reads as the same line repeated five times and files a self-report. This moves the first announcement to INFO; dedupe, ledger and note behaviour are unchanged.
Same shape as #17297 (deferred base refresh to debug) and #17519 (freshness-guard line below WARN). The existing tests' log handlers filtered at Warn, so they now use Info, and a new test pins the announcement at
level=INFO.β hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88