Skip to content

Owner decision: verify deployment and enable Hive admission to GitHub merge queues #1605

Closed

Description

@hanthor

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 main bases, through auto_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 downstream merge_group workflows. 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 MERGE for 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

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_group required 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.

Activity

  1. added
    needs-kindA maintainer must classify this issue; the intake source did not establish its kind.
    on Nov 1, 2026
  2. castrojo commented on Nov 1, 2026

    @castrojo
    Contributor

    This looks insane, I love it!

  3. added
    triage/acceptedScope accepted; ready for work. Use `/triage accepted`.
    on Nov 1, 2026
  4. castrojo commented on Nov 1, 2026

    @castrojo
    Contributor

    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!

  5. changed the title [-]Owner decision: enable Hive-owned merge queues for Utah and utah-packages[/-] [+]Owner decision: verify deployment and enable Hive admission to GitHub merge queues[/+] on Nov 1, 2026
  6. added
    stage/045-needs-decisionIssue parked on a person: needs-human or a maintainer decision is owed before the hive picks it up
    and removed
    stage/010-actionableTriaged; eligible for the hive to pick up
    on Nov 1, 2026
  7. Danathar commented on Nov 18, 2026

    @Danathar
    Contributor

    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 zero merge_group runs 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):

    • Ruleset 22705163 got a merge queue at 1:49 PM EST: squash, groups of up to 5, 5 building at once, ALLGREEN, 120-minute timeout.
    • The hive's native_merge_queue and squash_only settings list the repo since 1:50 PM EST.
    • First merge through the queue: fix(ci): page past 1000 artifacts when publishing and staging a full rebuild utah-packages#1204, queued by @hanthor. Its group ran Canary, Unit tests and Runtime contract, all green, with the build passes skipped, and it merged at 1:52 PM EST (squash afd014c0).
    • Still pending: the first PR the hive queues itself, after which the strict "up to date" rule comes off.

    utah (now):

    • Same queue settings, added to ruleset 22705160. contract and build_main / Check all testing builds successful stay required, and the strict rule stays until the first group passes. merge-queue.yml reports build_main on the queue commit, building every flavor locally and publishing nothing.
    • The hive's native_merge_queue gets projectbluefin/utah#main. utah is already squash_only.

    Competing admission (the Prow point above): utah's Prow still merges /lgtm + /approve PRs with the workflow GITHUB_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 /lgtm merge 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 with prow-run.yml. That's left to James.

    Undo: remove the merge_queue rule from 22705163 or 22705160, and take the repo off auto_merge.native_merge_queue.

  8. Danathar commented on Nov 18, 2026

    @Danathar
    Contributor

    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_queue by hivecommons-hive[bot] at 1:57 PM EST, so it was queued by the hive's App, not a person.
    • Its group gh-readonly-queue/main/pr-1335-d67dd762… ran both required checks, and both passed: contract (Build Utah, run 44375372381) and build_main / Check all testing builds successful (Merge queue image build, run 44375371529).
    • It merged at 2:08 PM EST as squash 6deb0c6d.

    Change: in ruleset 22705160, strict_required_status_checks_policy went from true to false. That was the only change: the merge queue and both required checks stay. The queue now tests each PR on top of main and the entries ahead of it, so open PRs no longer need to rebase after every merge.

    Undo: set strict_required_status_checks_policy back to true in 22705160.

    utah-packages keeps the strict rule until the hive's first queued PR there goes through. #1201 and #1199 are lined up.

  9. Danathar commented on Nov 20, 2026

    @Danathar
    Contributor

    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):

    Reopen this if either queue needs to change.

  10. removed
    stage/045-needs-decisionIssue parked on a person: needs-human or a maintainer decision is owed before the hive picks it up
    on Nov 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    approved-directionneeds-kindA maintainer must classify this issue; the intake source did not establish its kind.triage/acceptedScope accepted; ready for work. Use `/triage accepted`.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions