Repository navigation
Closed
Labels
bugSomething isn't workingSomething isn't workinghelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
Description
Problem
Every PR comment and every review the hive posts emails the PR author and everyone watching the repository. The hive is spamming. Measured on hivecommons/hive today:
- PR 🐛 activity monitor: 'merging now' lingers, silent merges, closed rows vanish #15817 (2 hours): 8 bot issue comments + 3 bot reviews.
<!-- hive:human-071-note head=… -->posted three times (once per new head, each @-mentioning @clubanderson).<!-- hive:stage-regressed -->×3: 080→071, and 080→050 twice with reasonrequired-check-pending— that is not a regression, CI simply restarted after a push.<!-- hive:stage-stalled -->: "no activity for 30m: merge-train:queued-behind…" — being queued behind the train front is not stalled.<!-- hive:create-pr-duplicate-guard -->.
- PR ✨ stage tracker: PR sub-row names the other issues it also closes #15834: 5 bot reviews (2 of them "Reviewed — no findings from this perspective." from the adjudicator) + 3 comments.
- PR 🐛 Merge train seats only PRs green and reviewed on their current head; regressed members are ejected #15831: 5 reviews + 5 comments.
Multiply by ~30 open PRs and every watcher receives dozens of emails an hour, none of which say anything the Activity Monitor (stage tracker), the evidence bundles and the stage labels do not already say.
Expected
Cut hive-generated GitHub notifications on PRs by ≥80 % with no loss of information:
- One hive status comment per PR, edited in place. Stage stalled/regressed notes, the 071 note and the duplicate-guard redirect are sections of a single
<!-- hive:status -->comment that is created once and PATCHed afterwards (edits do not email). - No per-perspective "no findings" reviews. A clean perspective records its verdict through the relay / evidence bundle only. Only perspectives with findings post, and a head carries one hive review; later findings for the same head join it instead of becoming another review.
- Stage-regressed only when something actually failed;
required-check-pendingafter a push is not a regression. Stage-stalled never fires formerge-train:queued-behind*, rebasing, base refresh, or any other state the hive itself controls. - @-mentions only when a human action is genuinely required, once per PR per distinct cause — not once per head.
- Config knob
github.notifications.mode(quietdefault |normalrestores today's behaviour), documented with the reason: every comment emails authors and watchers.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workinghelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
Activity