Repository navigation
Closed
2 / 22 of 2 issues completed
Copy link
Labels
has-open-prhelp 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
Spam reducer #3c, from the 2026-11-07 comment audit (hivecommons/hive, 10-27 β 11-07, GraphQL sample of bot comments per item).
Evidence
| day | hive:contributor-nudge |
unmarked bot free-text (hive:origin footer only) |
|---|---|---|
| 11-03 | 11 | β |
| 11-04 | β | 30 |
| 11-05 | 34 | 46 |
| 11-06 | 13 | 32 |
hive:contributor-nudgerebound 11 β 34/day on 11-05.src/pkg/github/automerge/automerge_contributor_nudge.goposts one nudge comment per head (plus a stall re-nudge, cap 2 per head); every push to a red clanker PR re-arms it, so a PR that is red for the same reason across several heads collects a new@authorcomment on each push.- Unmarked agent free-text 30β46/day since 11-04. Agent
gh pr commentbodies relayed throughbin/gh-wrapper.shcarry only the identity footer +<!-- hive:origin β¦ -->marker (src/pkg/github/attribution.go,attributionIdentityFooter). Reducer π± Sync workflows from kubestellar/infraΒ #1 (π Fold hive PR notes into one edited status comment and stop no-findings review spamΒ #15876/π fix: fold remaining hive comments into the status comment in quiet modeΒ #15919) folded the hive's own status notes into one editedhive:statuscomment and reducer docs: add EXECUTOR MODE pattern and multi-agent topologyΒ #2 (π Edit claim ledger, needs-decision and sentinel comments in place; suppress reviewer-lane no-findings reviewsΒ #16434) did the same for the claim ledger, but origin-footer free-text still lands as a fresh comment every time. - No guard keeps new emitters from bypassing the marker/upsert helpers: 54 raw
CreateCommentcall sites inpkg/github+pkg/github/automergehave no marker in their enclosing function.
Fix
- Nudge once per PR + reason. Marker
<!-- hive:contributor-nudge reason=<slug> head=β¦ n=β¦ mode=β¦ -->; the sweep edits the hive's existing nudge comment in place (same mechanism as the 085/090 entry upsert) when the reason changes or a new head is red for the same reason, instead of posting another copy. Escalation: at most one re-nudge afterauto_merge.nudge_repeat_after(default 72h) while the same reason persists, then stop. The relayfix-prdispatch and the adoption-grace ledger are unchanged. - Origin-footer free-text relayed through the issue-request watcher: in quiet notification mode it becomes a section of the upserted
hive:statuscomment; otherwise one edited<!-- hive:origin-notes -->comment per PR carries the notes. - Marker ratchet test (
internal/testutil, grep-based like the sleep ratchet): every raw comment emitter inpkg/githubandpkg/github/automergemust carry ahive:marker in its enclosing function, with an allow-list for transport primitives; the baseline is the current count so it can only go down.
Out of scope here (sibling PRs): review_backlog.go / review_severity.go, the hive:signoff-attribution and hive:unauthorized emitters.
Metadata
Metadata
Assignees
Labels
has-open-prhelp 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
hivecommons-hive commentedon Nov 7, 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)π fix(automerge): upsert contributor-nudge comments once per PR + reaβ¦
hivecommons-hive commentedon Nov 7, 2026
All children delivered: #17084, #17085.
Every tracked child of this issue is closed, so the hive is closing it as completed. Reopen it if something it asked for is still missing.
github-actions commentedon Nov 7, 2026
@clubanderson this issue was closed by @hivecommons-hive[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.stagelabels: cover MarkNudgedReason, NudgeReasonSlug and NudgeStart
π± contributor-nudge once per PR+reason; fold origin notes into statusβ¦