Skip to content

Show profile routing context in the profile chooser #320

@rianjs

Description

@rianjs

Problem

The cr init profile chooser currently lists profile names without showing where each profile will run. For a user editing a profile, that routing context is the most important piece of information: it answers “what is this reviewer, and where should it apply?”

The chooser also puts the default profile alongside named/routed profiles without making its fallback behavior explicit.

Desired behavior

Render profile choices from most-specific to least-specific routing behavior, and show each profile's automatic selection routes under the profile name.

Target shape:

Choose a profile to edit or create.

Review Profile

monit
github.com/SignalFT; github.com/OtherMonitOrg
open-cli-collective
github.com/open-cli-collective
rianjs
github.com/rianjs
default
Everything else

Create new profile
Back to main menu

Details:

  • Show route entries under each profile as ; -concatenated text.
  • Render route summaries in the softer secondary/description color.
  • Keep keyboard highlighting behavior the same when arrowing over profile rows.
  • Treat the default profile as the least-specific fallback and describe it as Everything else.
  • Coordinate with Refine init inventory menu section labels and spacing #318 so pseudo-section labels like Actions are not attached to selectable rows.

Specificity ordering guidance

Prefer an order that helps users reason about routing:

  • Profiles with explicit repository routes before broader namespace/org routes.
  • Routed profiles before the default fallback profile.
  • Stable deterministic tie-breaking for profiles with equivalent specificity, such as by profile name.

Acceptance criteria

  • Profile chooser rows include route context where available.
  • Route summaries are displayed with ; delimiters, not newline-only formatting.
  • The default profile appears last among profiles and is labeled as the fallback (Everything else).
  • The existing Create new profile and Back to main menu actions remain available.
  • Tests cover profile ordering and route-summary rendering.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:surfaceUser-visible command surface and lifecycle commandsenhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions