Skip to content

👥 Team ownership mode — single-owner assignment for github-issue-ops (EPIC) #88

Description

@shouze

Why

--group-by-team-prefix groups repos by GitHub team to visualise ownership across an organisation. However, some repos belong to multiple teams simultaneously and appear under combined sections like squad-frontend + squad-mobile.

github-issue-ops requires a single owner per item (repo or extract) to route and assign issues without ambiguity. This EPIC introduces the TUI + CLI tooling to resolve multi-team ownership before piping output downstream.

Sub-issues

Issue Feature Priority Scope
#85 Team pick mode — p on a multi-team section header to assign it to a single team + --pick-team replay flag 🔴 MVP good first issue
#86 Team dispatch — split a multi-team section by assigning each repo/extract to one team 🟡 Future maintainer
#87 Team merge — undo a dispatch and restore the combined section 🟢 Nice-to-have maintainer

Scope

#85 is the MVP: it covers the most common case — resolving the ambiguity of a combined section by picking a single owner directly from the TUI. It is scoped as a good first issue.

#86 and #87 address fine-grained dispatch at the repo/extract level. They require the section infrastructure introduced by #85 and are reserved for a maintainer.

CLI surface summary

Flag Introduced in Purpose
--pick-team "<A + B>"=<chosen> #85 Assign a combined section to a single team; = separates the combined label from the chosen team
--dispatch <team>=<refs> #86 Assign specific repos/extracts to a single team

All ref formats in --dispatch follow existing conventions: repo short-name (repoA) or extract ref (repoA:src/foo.ts:0), consistent with --exclude-repositories and --exclude-extracts.

Relationship to the roadmap

This EPIC replaces the two separate entries in #63:

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions