Repository navigation
Closed
Labels
agent/dedupeCreated by Hive for agent-filed issue provenanceCreated by Hive for agent-filed issue provenancehelp 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
Decision required: yes
Risk: security posture (choosing which merge-gate hardening PR survives)
Summary
Triage pass over the 28 open issues and 7 open PRs in hivecommons/hive as of 2026-11-03. Found 1 near-duplicate issue pair, 1 duplicate PR pair, 1 missing PR↔issue link, and 1 conflicting-PR pair — all in the human_merge_pin_only exception family (#16242). No actions have been taken; this is a checklist for maintainers.
Near-duplicates: close one
| Keep | Merge into it | Reason |
|---|---|---|
| #16399 [sec-check] human_merge_pin_only waives hold on author login alone | #16380 [reviewer] Pin-only exception trusts PR opener login | Same finding: humanMergePinOnlyExempt derives trust solely from pr.GetUser() login (both cite src/pkg/github/automerge/automerge_human_paths.go:97 / the trusted_authors match). #16380 is exactly point 1 of #16399; #16399 is broader (adds the action-SHA fork-network reachability gap) and carries the concrete recommendations. |
| PR #16400 require verified trusted-author commits | PR #16394 tighten pin-only exception trust check | Same semantic change in the same helper: both make humanMergePinOnlyExempt + /approve require every head commit to be trusted-authored and fail closed on an unreadable/incomplete commit list, editing the same four files (automerge_human_paths.go, pr_approve_command.go + their tests). #16400 is strictly stronger — it additionally requires GitHub-verified signatures and the web-flow/trusted committer rule (which is what makes the author login non-spoofable), and updates docs/hive-merge.md + the operator reference. |
- 🐛 fix(automerge): tighten pin-only exception trust check #16394 — close as superseded by PR 🐛 fix(automerge): require verified trusted-author commits for the pin-only exception #16400 (same fix, weaker: no signature verification)
- [reviewer] Review backlog (security): Pin-only exception trusts PR opener login, not the pushed commits #16380 — close as duplicate of [sec-check] human_merge_pin_only waives the human-merge-path hold on PR author login alone — head commits and action SHA upstream reachability are never verified #16399 point 1 (note: [reviewer] Review backlog (security): Pin-only exception trusts PR opener login, not the pushed commits #16380 is
hive:blocked-onPR ✨ feat(automerge): enforce the human-merge pin-only exception in the sweep gate and /approve #16377 and auto-managed; closing it manually ends that tracking)
PR ↔ issue links to add
- PR 🐛 fix(automerge): require verified trusted-author commits for the pin-only exception #16400 fixes exactly what [reviewer] Review backlog (security): Pin-only exception trusts PR opener login, not the pushed commits #16380 reports (login-only trust in
humanMergePinOnlyExempt) but does not reference it — verified via [reviewer] Review backlog (security): Pin-only exception trusts PR opener login, not the pushed commits #16380's timeline and 🐛 fix(automerge): require verified trusted-author commits for the pin-only exception #16400's commits/comments. If 🐛 fix(automerge): tighten pin-only exception trust check #16394 is closed per above, itsCloses #16380goes with it; addCloses #16380to PR 🐛 fix(automerge): require verified trusted-author commits for the pin-only exception #16400's body so the issue does not stay open as noise.
Conflicting PRs: merge order matters
- PR ✨ feat(github): enforce pin-only exception in merge-request relay #16398 (relay enforcement,
Fixes #16265) and PR 🐛 fix(automerge): require verified trusted-author commits for the pin-only exception #16400 both touchsrc/pkg/config/automerge_pin_only.go,src/docs/hive-merge.mdandsrc/docs/operator-reference/README.mdwith different semantic changes — whichever lands second must rebase those three files. More importantly: ✨ feat(github): enforce pin-only exception in merge-request relay #16398's merge-request relay grants the exception on author login alone, the exact trust model 🐛 fix(automerge): require verified trusted-author commits for the pin-only exception #16400 removes from the sweep//approvepath (and the gap [sec-check] human_merge_pin_only waives the human-merge-path hold on PR author login alone — head commits and action SHA upstream reachability are never verified #16399 reports). If ✨ feat(github): enforce pin-only exception in merge-request relay #16398 lands as-is after 🐛 fix(automerge): require verified trusted-author commits for the pin-only exception #16400, the relay becomes the one remaining login-only surface; the relay should call the shared commit-provenance helper, or [sec-check] human_merge_pin_only waives the human-merge-path hold on PR author login alone — head commits and action SHA upstream reachability are never verified #16399's fix must be extended to it.
Checked and not duplicates
- PR 🐛 fix(automerge): gate normal-mode stage-note comments #16396 ↔ [reviewer] Review backlog (intent-alignment): Normal-mode stage-note create remains a raw go-github CreateComment #16393 — stage-note raw CreateComment;
Fixes #16393present, disjoint files from the pin-only cluster despite sharing the automerge package. - PR ✨ feat(github): enforce pin-only exception in merge-request relay #16398 ↔ [scanner] human-merge pin-only exception: enforce in merge-request relay #16265 —
Fixes #16265present in the PR body. - feat: bounded trusted pin-only exception to per-repository human-merge paths #16242 ↔ [sec-check] human_merge_pin_only waives the human-merge-path hold on PR author login alone — head commits and action SHA upstream reachability are never verified #16399 — feat: bounded trusted pin-only exception to per-repository human-merge paths #16242 is the feature tracker for the pin-only exception; [sec-check] human_merge_pin_only waives the human-merge-path hold on PR author login alone — head commits and action SHA upstream reachability are never verified #16399 is a finding against its implementation, not a duplicate of it.
Filed by dedupe agent (issues-only mode). Recommendations only — nothing has been closed, labelled, or merged.
🐝 Hive Agent: dedupe | Instance: hosted-available-oke-11-placeholder-r05x | SHA: unknown
— hive: agent=dedupe backend=copilot model=claude-fable-5 copilot=1.0.88
Metadata
Metadata
Assignees
Labels
agent/dedupeCreated by Hive for agent-filed issue provenanceCreated by Hive for agent-filed issue provenancehelp 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 3, 2026
What to reply
/hive approve: go with the recommendation/hive decision <your instructions>: go ahead, following your instructions/hive help: show these againIf what this issue waited on has been done (a merged fix, or an action taken outside this repository), a maintainer can reply
/fixedto close it as completed; Hive clears its park labels.Only a maintainer with write access can un-park; everything else is ignored. Full command reference: https://github.com/hivecommons/hive/blob/v5/src/docs/maintainer-commands.md.
hivecommons-hive commentedon Nov 3, 2026
Closed as read (advisory acknowledged) by @clubanderson from the Hive dashboard.