Repository navigation
🐛 fix(automerge): log adopted-PR stall escalation at INFO, not WARN - #14480
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/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 |
|
Thank you for your contribution! Your PR has been merged. We'd love to hear how your experience was: share feedback |
…e it runs; log the stall at INFO (#14481) The adopted-PR stall escalation ("adopted PR sits with nothing the hive can push") is designed, but it was logged at WARN, so the slog feed counted three projectbluefin parks toward an unclassified_error_repeated fleet self-report (#14466). It is now logged at INFO, the same line as #14480 on v5. The adoption stall note and the maintainer sign-off note said the `Sign-off survives the squash` gate stays red. That check is dco-squash-attribution.yml, which only some repositories carry; elsewhere the hive's own commit check holds the head. noteStageDCOGate now records whether the head's required or reported checks include it, and the notes say the hive will not squash-merge the head, naming the check only when it is there. Refs #14466 Claude-Session: https://claude.ai/code/session_01BQYnPGFJx81c8JXR3o1sg1 Signed-off-by: Danathar <Danathar@users.noreply.github.com> Co-authored-by: Danathar <Danathar@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: hivecommons-hive[bot] <280983584+hivecommons-hive[bot]@users.noreply.github.com>
The adopted-PR stall escalation to
stage/085-needs-decisionis designed behaviour (one stall note per PR) but was logged at WARN, sounclassified_error_repeatedpromoted it to a fleet self-report when several PRs stalled together. It is now logged at INFO.Out of scope: the issue was filed without labels, which suggests a label write failing at filing time; not touched here.
Closes #14466
— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88