Repository navigation
Description
Decision needed
Choose and authorize the production merge-admission owner for projectbluefin/utah#main and projectbluefin/utah-packages#main so routine refresh → CI → landing runs without maintainer babysitting.
Recommendation: use the existing Hive GitHub App for native GitHub merge-queue admission; let GitHub test the synthetic merge group and perform the landing. Keep the deployed App-based freshness + protected auto-merge workflows as the interim path until a live pilot succeeds.
Owner actions
- Confirm the deployed Hive version supports native queue handoff and provide an authenticated owner/operator to configure it. The hosted dashboard at https://hive.hivecommons.dev/dashboard redirects this session to login; no authenticated deployment/configuration access was available.
- Approve native handoff scoped only to these two repositories and their exact
mainbases, throughauto_merge.native_merge_queue. Keep “queue owns freshness” off until the pilot proves the replacement path. - Resolve competing admission in Utah: its Prow workflow currently uses
GITHUB_TOKEN, whose mutations cannot reliably trigger downstreammerge_groupworkflows. Select one admission owner while preserving existing review commands and exact-head LGTM binding; do not simply disable Prow functionality. - Confirm the queue merge method preserves the required authorship/DCO policy. Hive may require
MERGEfor mixed-authorship changes.
Hive's documented enqueue path uses its existing contents/PR-write installation permissions; it does not require a wider Hive grant. If the owner chooses an App-token Prow cutover instead, the current Mergeraptor installation additionally needs owner-approved statuses:write and actions:write grants to preserve LGTM and /test/retest/ok-to-test behavior. Existing secrets alone do not supply those grants.
Upstream mechanism and rollout guidance: https://github.com/hivecommons/hive/blob/v5/src/docs/native-merge-queue.md
Already completed
- Merge-group trigger support landed: Utah ci: run required checks on merge_group utah#1052 and packages ci: run required checks on merge_group utah-packages#859. Packages' proof checks the whole synthetic pipeline tree; a docs-only member cannot bless another member's pipeline changes.
- Interim App-based freshness/landing automation landed: Utah ci: keep approved auto-merge candidates current without manual updates utah#1055 and packages ci: land built bumps and refresh armed PRs without manual intervention utah-packages#863.
- Real App-authored behind-branch update triggered fresh CI: https://github.com/projectbluefin/utah-packages/actions/runs/41251651021.
- Fork cleanup/automatic proof-refresh repair landed in fix: prevent concurrent fork Canary cleanup from blocking proof refresh utah-packages#865; approved fork PRs ci: add docs-hygiene pre-commit checks #838 and ujust changelogs shows bluefin, not bluefin-lts #819 subsequently passed exact-head proof and auto-merged.
Current state: native queue requirements are not enabled. Effective main rules in both repositories retain strict current-base freshness and their original GitHub Actions-bound required checks. Green PR-head checks are not evidence of a successful synthetic-group run.
Acceptance / close criteria
- Record the owner decision and responsible operator; confirm deployed configuration/version, not just upstream source support.
- Configure the exact repository/base scopes and a single admission owner without losing review/hold controls.
- Run a controlled single-entry pilot: observe App enqueue of the reviewed exact head, actual synthetic
merge_grouprequired checks, and a merged receipt. No fabricated success contexts or check-provider changes. - Verify a failing required check prevents landing and document rollback/drain behavior before expanding the rollout.
- Enable the production queue policy only with pilot evidence; document final policy and ownership in the appropriate common/repository skills.
Human intervention should remain for trust/security/policy/runtime-acceptance exceptions, not routine refresh, CI, and merge handling. This issue requests an owner decision and deployment access; it does not authorize bypassing checks or privileged fork review.
Feature availability clarification
“Hive-owned merge queue” is not the UI feature name and does not mean Hive implements a separate merge engine. This is Hive admission to GitHub native merge queues.
- Backend handoff merged into upstream Hive in ✨ feature: enqueue eligible PRs into GitHub native merge queues hivecommons/hive#15308 on 2026-10-30.
- Settings UI/integration merged into upstream
v5in ✨ Complete native GitHub queue CI and policy integration hivecommons/hive#15853 on 2026-10-31. - Current upstream UI labels it Settings → Features → Auto-Merge → Native GitHub merge queue. Actual UI source: https://github.com/hivecommons/hive/blob/v5/src/pkg/dashboard/static-src/js/config-features.js#L483-L506.
- The user cannot find this control in their Hive. The deployed version and bundled UI have not been verified. First establish whether these changes are deployed; do not assume the remaining action is merely enabling an existing setting. Source availability, deployment, Hive opt-in and GitHub queue policy are distinct states.
Activity
castrojo commentedon Nov 1, 2026
This looks insane, I love it!
castrojo commentedon Nov 1, 2026
The way I've been doing this is by just setting the hurny stuff like renovate bumps into mostly automated, we can set them to automerge for patch releases, etc and gate the major ones.
This would be way smarter though, would love to try it!
[-]Owner decision: enable Hive-owned merge queues for Utah and utah-packages[/-][+]Owner decision: verify deployment and enable Hive admission to GitHub merge queues[/+]🐛 fix(contribute): a needs-decision park posts its question (#16837)
Danathar commentedon Nov 18, 2026
Status, 11-18: the merge queue is on for utah-packages and is being turned on for utah (Doug, maintainer; @hanthor confirmed both on Discord this afternoon, after choosing the queue on projectbluefin/utah-packages#304).
Before today: neither repo had a merge-queue rule on
main. GitHub showed zeromerge_groupruns in both repos. The groundwork listed above (utah#1052, utah-packages#859) was in place, but the switch had never been flipped.utah-packages (done):
ALLGREEN, 120-minute timeout.native_merge_queueandsquash_onlysettings list the repo since 1:50 PM EST.Canary,Unit testsandRuntime contract, all green, with the build passes skipped, and it merged at 1:52 PM EST (squashafd014c0).utah (now):
contractandbuild_main / Check all testing builds successfulstay required, and the strict rule stays until the first group passes.merge-queue.ymlreportsbuild_mainon the queue commit, building every flavor locally and publishing nothing.native_merge_queuegetsprojectbluefin/utah#main. utah is alreadysquash_only.Competing admission (the Prow point above): utah's Prow still merges
/lgtm+/approvePRs with the workflowGITHUB_TOKEN, and GitHub won't start queue checks for that. In practice it isn't used: of utah's last 60 merges (since 11-09), the hive did 22, @hanthor 19, MergeRaptor/Renovate 11, Danathar 7, castrojo 1, and Prow 0. All of those paths work with the queue. A Prow/lgtmmerge would wait in the queue until it times out (120 min), and clicking Merge then works. The lasting fix is switching Prow's lgtm job to the MergeRaptor App token, as common#1700 does withprow-run.yml. That's left to James.Undo: remove the
merge_queuerule from 22705163 or 22705160, and take the repo offauto_merge.native_merge_queue.Danathar commentedon Nov 18, 2026
utah: the first PR the hive queued went through, so the strict "up to date" rule is off (2:12 PM EST, 11-18).
Evidence: projectbluefin/utah#1335 (MergeRaptor's wallpapers digest bump).
added_to_merge_queuebyhivecommons-hive[bot]at 1:57 PM EST, so it was queued by the hive's App, not a person.gh-readonly-queue/main/pr-1335-d67dd762…ran both required checks, and both passed:contract(Build Utah, run 44375372381) andbuild_main / Check all testing builds successful(Merge queue image build, run 44375371529).6deb0c6d.Change: in ruleset 22705160,
strict_required_status_checks_policywent fromtruetofalse. That was the only change: the merge queue and both required checks stay. The queue now tests each PR on top ofmainand the entries ahead of it, so open PRs no longer need to rebase after every merge.Undo: set
strict_required_status_checks_policyback totruein 22705160.utah-packages keeps the strict rule until the hive's first queued PR there goes through. #1201 and #1199 are lined up.
Danathar commentedon Nov 20, 2026
Closing as completed: every owner action here is done, in both repos (Danathar, maintainer, 11-19).
Evidence (checked live 11-19, 8:14 PM EST):
main: squash merge in both repos, in utah ruleset 22705160 and utah-packages ruleset 22705163.hivecommons-hive[bot]and merged through the queue at 2:08 PM EST on 11-18.hivecommons-hive[bot]and merged through the queue at 2:54 PM EST on 11-18.strict_required_status_checks_policyis false in both rulesets, so open PRs no longer need a rebase after every merge.prow.ymlnow runs Prow with the MergeRaptor App token instead ofGITHUB_TOKEN, so merge-queue runs trigger. utah-packages has no Prow workflow.Reopen this if either queue needs to change.