diff --git a/changelog.d/changed-upsert-signoff-unauthorized-nudge.md b/changelog.d/changed-upsert-signoff-unauthorized-nudge.md new file mode 100644 index 0000000000..a6077abb8b --- /dev/null +++ b/changelog.d/changed-upsert-signoff-unauthorized-nudge.md @@ -0,0 +1 @@ +- Hive no longer posts a new stage-072 contributor nudge on every push to a red contributor-agent PR ([#17067](https://github.com/hivecommons/hive/issues/17067)). On 2026-11-05 the nudge reached 34 comments a day. Each PR now keeps one `hive:contributor-nudge` comment, and its marker carries `reason=`. A new head that is red for the same reason, or a change of reason, edits that comment in place, which notifies nobody. If the same reason lasts longer than the new `auto_merge.nudge_repeat_after` setting (default `72h`), the hive posts one fresh re-nudge, then goes back to editing. Existing per-head nudge comments are adopted and rewritten in place. The relay `fix-pr` dispatch and the adoption grace are unchanged. diff --git a/src/cmd/hive/merge_eligibility.go b/src/cmd/hive/merge_eligibility.go index a3512f8f8c..3673c297b1 100644 --- a/src/cmd/hive/merge_eligibility.go +++ b/src/cmd/hive/merge_eligibility.go @@ -115,6 +115,7 @@ func stageLabelPolicyFunc(cfg *config.Config) func() automerge.StageLabelPolicy StalledRequireQuiet: stage.Stalled.IsRequireQuiet(), ContributorNudge: stage.ContributorNudge.IsEnabled(), RenudgeInterval: stage.ContributorNudge.EffectiveRenudgeInterval(), + NudgeRepeatAfter: cfg.AutoMerge.EffectiveNudgeRepeatAfter(), Adoption: stage.Adoption.IsEnabled(), GraceOnline: stage.EffectiveContributorGraceOnline(), GraceOffline: stage.EffectiveContributorGraceOffline(), diff --git a/src/docs/hive-merge.md b/src/docs/hive-merge.md index d56f26b65d..4c42690afd 100644 --- a/src/docs/hive-merge.md +++ b/src/docs/hive-merge.md @@ -1236,9 +1236,11 @@ when the copy is closed without merging (`adopted_by_state` closed / closed-twice / copy-failed). A clanker PR entering `stage/072-returned-to-contributor` also triggers the -contributor nudge: the sweep posts one `` comment per head naming the failing checks / review asks (re-nudged -once at the stall threshold, cap 2) and hands the diagnosis to the contribute +contributor nudge: the sweep keeps one `` comment per PR naming the failing checks / review asks +(due once per head and once more at the stall threshold, cap 2; a due nudge +edits that comment in place, and a fresh one is posted only once, after the +same reason persisted for `auto_merge.nudge_repeat_after`) and hands the diagnosis to the contribute hub, which — when the author's relay heartbeat is fresh — pushes a `fix-pr` interrupt task into their relay session (parallel sub-session or preempt, per the relay's declared capability) under a per-contributor fix budget; diff --git a/src/docs/labels-and-control-signals/stage-labels.md b/src/docs/labels-and-control-signals/stage-labels.md index 92c16796a0..ff3af9223c 100644 --- a/src/docs/labels-and-control-signals/stage-labels.md +++ b/src/docs/labels-and-control-signals/stage-labels.md @@ -753,12 +753,17 @@ When a contributor-agent PR goes red the hive does not just relabel it (a human- [hive-merge.md](../hive-merge.md#stage-labels)): 1. `stage/072-returned-to-contributor` and ONE `` comment - @-mentioning the author with the failing checks / review asks and "reply - here or push a new head". Re-posted only for a new head; re-nudged once - more after `governor.labels.stage.contributor_nudge.renudge_interval` - (default = the stage's 24h dwell, i.e. at `stage/stalled`), then no more - — **cap: 2 nudges per head**. `mode=` records how the relay side was + reason= head= n=<1|2> mode= + since=