Repository navigation
Description
Requested capability
Add an explicitly configured, fail-closed exception for authenticated, trusted pin-only maintenance to the per-repository human-merge-path gate. Do not remove the underlying protection for other changes.
Concrete consumer / approved policy
projectbluefin/utah#1082 owns the rollout for Utah and utah-packages. Its maintainer-delegated decision is recorded at projectbluefin/utah#1082 (comment). That decision permits a narrow automatic lane; it does not authorize arbitrary workflow changes, broader credentials or a branch-protection bypass.
The former common-image issue was moved to Utah and its docs-only proposal projectbluefin/common#1617 was closed. This issue is for actual Hive controller enforcement, not another policy document in the image repository.
Observed source boundary
At inspected upstream commit e60f06f:
- https://github.com/hivecommons/hive/blob/e60f06f268d875ff68435658614f5a571fe561b8/src/pkg/github/human_merge_paths.go — merge-request relay refuses configured path matches and applies hold.
- https://github.com/hivecommons/hive/blob/e60f06f268d875ff68435658614f5a571fe561b8/src/pkg/github/automerge/automerge_human_paths.go — automerge sweep applies the corresponding gate.
These inspected gates do not classify a match into pure-pin vs privilege/trust-changing edits. Emptying the path list would remove protection for both. This is a source-level observation at the linked commit, not a claim about the deployed controller version.
Existing issues #11027/#11036/#11038/#11039 establish/enforce the path gate; #15386 fixes glob matching. Searches for human_merge_paths and pin-only did not identify an existing bounded-exception implementation issue. Reuse/link an existing implementation if one exists under different terminology; do not create parallel enforcement.
Required behavior
- Opt-in, per repository and allowed update class; preserve current path-gate behavior when unconfigured.
- Require already-trusted authenticated authors, a complete exact-head diff, only existing approved pin/reference updates, and review of the referenced upstream change. SHA-shaped text alone is not a safety proof.
- No new workflow logic, steps, sources, owners, permissions, credential use, signing/provenance or trust-boundary changes under this exception.
- Preserve actual native required checks and producer bindings, strict freshness, current review, substantive objections, unrelated holds and the existing configured soak. Incomplete/unknown evidence fails closed.
- Apply consistent admission in every relevant merge path, including the relay/sweep and native-queue admission if supported. Do not make one route an escape hatch.
- Attribute path-only holds so policy may resolve only its own stale hold after qualification. Never clear a human/security/unrelated hold just because the diff looks like a pin bump.
Acceptance
- Implement the actual controller enforcement/configuration, not only documentation; link the implementation PR and configuration schema.
- Exercise eligible pure-pin, mixed permission+pin, untrusted author, incomplete file list, changed head, substantive review findings and missing required evidence through the real admission behavior.
- Preserve existing behavior for repositories that have not opted in, and prove no alternate merge route bypasses the gate.
- Document the actual operator configuration/reload path and deployed version needed by the Utah rollout; do not assume the image repo contains this setting.
- Link deployment and live positive/negative evidence back to Hive rollout: deploy the approved bounded automatic merge policy for Utah projectbluefin/utah#1082. chore(deps): update projectbluefin/actions digest to cbf1ce0 projectbluefin/utah#1068 is a representative positive candidate only after then-current-head qualification, not advance authorization to merge its old head.
The owner policy choice is resolved for the named consumers. Implementation/deployment and evidence remain distinct; do not silently substitute documentation, manual hold removal or synthetic success checks.
Activity
hivecommons-hive commentedon Nov 2, 2026
🔒 Claimed by @mrbobbytables (contributor on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 30m0s without activity and renews while the work continues. Reply
/unclaimto release, or/claimto take it over if you outrank the holder.hivecommons-hive commentedon Nov 2, 2026
Decomposed: a complete, fail-closed implementation needs changes in about 9 source files: config, patch-carrying file listers, the classifier, relay + client + notifywire, and sweep + engine options + /approve + two cmd wiring sites. It also covers separate concerns such as hold attribution. Split into ordered children:
Deployment and live evidence for projectbluefin/utah#1082 remain on this parent.
🐝 Hive Agent:
scanner| Instance:hosted-available-oke-11-placeholder-r05x| SHA:unknown— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88
hivecommons-hive commentedon Nov 2, 2026
🔒 Claimed by @mendezr (contributor on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 30m0s without activity and renews while the work continues. Reply
/unclaimto release, or/claimto take it over if you outrank the holder.16 remaining items
github-actions commentedon Nov 3, 2026
PR #16300 has merged (#16300) and referenced this issue with a non-closing
Refs #16242rather than a closing keyword.This issue remains open because the merged PR did not use
Closes/Fixes/Resolves. If the fix should close it on merge, use a closing keyword in the PR body; use the opt-inhive: needs-confirmationmarker only when the reporter genuinely must verify before closure.hivecommons-hive commentedon Nov 3, 2026
Verified once after #16300 merged: the issue stays open on purpose. Landed so far — schema + classifier (#16300) and the sweep/
/approvegate (#16377). Still in flight — relay enforcement (#16398 for #16265), commit-level trust tightening (#16394 for #16380), and path-only hold attribution (#16269). Labelledhive/verified-open; no new PR opened here to avoid overlapping those branches.🐝 Hive Agent:
scanner| Instance:hosted-available-oke-11-placeholder-r05x| SHA:unknown— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88
hivecommons-hive commentedon Nov 3, 2026
Status check (scanner): of the remaining pieces listed in the last verification, #16380 (commit-level trust) is closed — the shared
PinOnlyCommitsTrusted/PinOnlyActionPinsUpstreamhelpers landed via #16400 — and #16269 (hold attribution + operator docs) is closed. The only remaining work is relay enforcement, open as #16456 (supersedes #16398, for #16265), which is CI-green atd3c0824and parked on a maintainer decision because it is the App's third unattended merge path through protected paths. No new PR opened here to avoid overlapping that branch; this issue closes once #16456 lands.🐝 Hive Agent:
scanner| Instance:hosted-available-oke-11-placeholder-r05x| SHA:unknown— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88
hivecommons-hive commentedon Nov 4, 2026
Coverage check (scanner, origin/v5 @ 7060ac6): no new PR is needed. Each remaining item already has a PR:
src/pkg/config/automerge_pin_only.go,src/pkg/intent/pin_only.go,src/pkg/github/pin_only_files_test.go)./approveand native-queue admission: merged in ✨ feat(automerge): enforce the human-merge pin-only exception in the sweep gate and /approve #16377 (src/pkg/github/automerge/automerge_human_paths.go,automerge_sweep.go,pr_approve_command.go, wired insrc/cmd/hive/main_sweeps.go). Native enqueue (automerge_native_queue.go) runs inside the sweep after this gate, so it is not a bypass route.src/pkg/github/human_merge_paths.go,merge_request_watcher.go,pin_only_provenance.go,client.goandsrc/cmd/hive/notifywire.go, plus docs. It is parked on an owner decision.Deployment and live evidence for projectbluefin/utah#1082 is not code and stays on this parent. This issue can close once #16456 lands and that evidence is linked.
— hive: agent=scanner backend=copilot
🐝 Hive Agent:
scanner| Instance:hosted-available-oke-11-placeholder-r05x| SHA:unknownhivecommons-hive commentedon Nov 4, 2026
PR #16607 covers this issue: #16607
The PR body says this is partial/non-closing work (
Refs/Part ofor leave-open wording), so Hive will not add a closing keyword. GitHub will not show its issue-list PR icon without a closing keyword; the stage comment is the link.hivecommons-hive commentedon Nov 7, 2026
All children delivered: #16262 → PR #16300, #16265 → PR #16607, #16266 → PR #16377, #16269 → PR #16293.
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
@hanthor 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.