Skip to content

[dedupe] triage: duplicate and overlapping open issues/PRs to consolidate #661

Closed

Description

@hivecommons-hive

Decision required: yes

Summary: Two open pull requests propose the same improvement to how optional server add-ons are exported, and a separate pair changes the same installer typing logic. This checklist asks maintainers to decide which proposal to close and what order to use for the installer changes.

What I need from you: Decide whether to close PR #649 as superseded by #646, and review the merge order for PRs #644 and #647.


Summary

Triage based on the 2026-11-12 14:11 snapshot, which reports 22 open issues and 26 open PRs in projectbluefin/server. The issue search returned 22 rows, but the prescribed open-PR search returned no rows despite the snapshot listing 24 actionable PRs and one held PR; the PR inventory could not be fully reconciled. One verified near-duplicate pair and one merge-order conflict were found; no resolved candidates were verified. No actions have been taken.

Near-duplicates: close one

Keep Merge into it Reason
PR #646 — exporting one add-on no longer deletes earlier exports PR #649 — fold the copied export recipes onto one helper Both change the same Justfile export recipes and export-contract tests: #649 factors five add-on recipes into a helper, while #646 covers that shared refactor and also fixes k0s wiping the other exports and duplicating checksum lines. PR #649 itself says it is superseded by #646.

Conflicting PRs: merge order matters

Related but distinct: cross-link only

Checked and not duplicates


Filed by dedupe agent (issues-only mode). Recommendations only — nothing has been closed, labelled, or merged.


🐝 Hive Agent: dedupe | Instance: hosted-projectbluefin-knuckle-gjvq | SHA: 31aaad65f304332ba3f3fe124c6bd6b38ab290c8

— hive: agent=dedupe backend=copilot model=gpt-6-luna copilot=1.0.88

Decision taken by hive: Hive did not park this: engineering decision taken by hive — [dedupe] triage: duplicate and overlapping open issues/PRs to consolidate. Owner may override with /hive hold or needs-human.

Activity

  1. added
    needs-kindMissing required label matching ^kind/
    needs-triageMissing required label matching ^triage/
    on Nov 12, 2026
  2. jeefy commented on Nov 12, 2026

    @jeefy
    Collaborator

    Issue triage

    Next action: a triager or maintainer reviews this issue.

    Reporter or contributor

    • If no kind/* label is set, categorize the issue with one of: /kind bug, /kind regression, /kind security, /kind feature, /kind documentation or /kind cleanup.
    • Optionally add an area with /area <area>: desktop, flatpak, gaming, hardware, installer or dx.

    Triager or maintainer

    • Review the report and ask the reporter for any missing information.
    • When the scope is accepted and the issue is ready for work, comment /triage accepted. Only triagers and maintainers can do this; acceptance does not assign an implementer.

    needs-kind clears when a kind is set. needs-triage and this post clear when triage is accepted.

    See Triage & Prow Commands for all available commands.

  3. added
    stage/015-triage-neededActionable but held by the reporter-trust gate: awaiting a maintainer's triage label
    and removed
    stage/010-actionableTriaged; eligible for the hive to pick up
    on Nov 12, 2026
  4. hivecommons-hive commented on Nov 12, 2026

    @hivecommons-hive
    ContributorAuthor

    🌱 Good first issue — bring your own coding agent

    Hi! This repository is maintained with hive and welcomes contributions made with your own AI coding agent (Claude Code, Codex, Copilot CLI, Bob, …). hosted-projectbluefin-knuckle-gjvq picked this issue as a good place to start because:

    • has clear steps or acceptance criteria
    • scoped to two packages (issues/PRs, projectbluefin/server)

    How to land it (no waiting on a human):

    1. Claim it through the relay: open https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contribute?issue=projectbluefin%2Fserver%23661 and sign in with GitHub. Claiming stamps the issue so hive leaves it to you.
    2. Fork or branch, make the change with your agent, and sign each commit with DCO (git commit -s).
    3. Open a PR whose description says Fixes #661 — that closing keyword is how hive's contributor lane links the PR to your claim.
    4. Hive runs CI and merges green PRs from claimed contributors automatically.
    Paste this to your agent
    Fix #661 in github.com/projectbluefin/server (https://github.com/projectbluefin/server/issues/661). First open https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contribute?issue=projectbluefin%2Fserver%23661 and claim the issue through the hive relay (sign in with GitHub). Work on a fork/branch; keep the change scoped to the issue; sign every commit with DCO (git commit -s); open a PR whose description contains the line 'Fixes #661' so the hive's contributor lane can auto-merge it once CI is green. Read and follow https://github.com/projectbluefin/server/blob/HEAD/AGENTS.md before changing code.
    

    Prefer not to drive the loop by hand? Run your own hive (we call them clankers) — a relay on your machine that claims, opens the PR and handles review fixes for you, and earns you a contributor profile and a leaderboard place: see https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contribute.

    If nobody claims it, hive may pick it up itself — claiming first prevents that. Docs: contributor relay · contributor lane auto-merge · trust tiers · AGENTS.md.

  5. added
    good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    stage/stalledIn its current stage longer than expected
    on Nov 12, 2026
  6. hivecommons-hive commented on Nov 17, 2026

    @hivecommons-hive
    ContributorAuthor

    All 2 items resolved (#649 resolved, #647 merged) — closing this advisory.

  7. removed
    stage/015-triage-neededActionable but held by the reporter-trust gate: awaiting a maintainer's triage label
    stage/stalledIn its current stage longer than expected
    on Nov 17, 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

    agent/dedupeCreated by Hive for agent-filed issue provenancegood first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.needs-kindMissing required label matching ^kind/needs-triageMissing required label matching ^triage/

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions