Repository navigation
feat: replace (Cloud-only) help sections with inline deployment badges - #767
Merged
Merged
Conversation
Root help grouping now mirrors the README's command tables: - Commands / Utilities / Continuous integration groups in README order (previously Utilities rendered first because group order followed first-member registration). login, info, and admin move to Utilities; config-manager and promote form the new Continuous integration group. - The (Cloud-only) command sub-sections are removed. Commands supporting exactly one deployment type render an inline [Cloud-only] badge in their description (generic: [Classic-only]/[ForgeOps-only] for the other types) via the same description-decoration mechanism as the stability badges — so every group stays alphabetical and the grouping no longer mixes "what the command configures" with "what it runs against". Badge color is magenta: the only hue clearing normal-text AA on both dark and light backgrounds that neither the stability palette nor any theme intent claims. - Stability badges render first, deployment second: [Preview] [Cloud-only] Manage direct configuration sessions. The README tables adopt the same [Cloud-only] badge notation, replacing the `*` suffix and its key-legend entries, so binary and docs share one convention. Option-level and environment-variable scoped sections (e.g. login's (Classic-only) options) are unchanged. Snapshots regenerated: 68 help snapshots plus one e2e usage-output snapshot. Full suite green: 633 suites / 1828 tests / 8486 snapshots. Co-Authored-By: Claude Code <noreply@anthropic.com>
debug and log move from Commands to Utilities, and dcc joins config-manager and promote in Continuous integration — matching the README's table membership exactly (programmatically verified: every root-level command now renders in the help group its README table names). Commander's implicit help command is routed to Utilities via the grouping callback, since it is created lazily and cannot be assigned a group at registration time. Snapshots regenerated; full suite green (633 suites / 1828 tests / 8486 snapshots). Co-Authored-By: Claude Code <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Root help grouping now mirrors the README's command tables, and the cloud-only grouping is replaced by an inline badge:
New group structure (same order as the README tables):
Commands:— the config-artifact familiesUtilities:— gainslogin,info,admin(previously buried alphabetically in Commands)Continuous integration:— new;config-managerandpromote(previously buried in Commands)Deployment badge replaces
(Cloud-only)sections. The old mechanism pulled single-deployment-type commands out of alphabetical order into(Cloud-only):sub-sections — and mixed two concepts (what a command configures vs. what it runs against). Now every command supporting exactly one deployment type renders an inline badge in its description, generic across all three deployment types ([Cloud-only],[Classic-only],[ForgeOps-only]), via the same description-decoration mechanism as the stability badges. Badges read left-to-right from command-nature to environment:[Preview] [Cloud-only] Manage direct configuration sessions.Badge color is magenta — the only hue clearing normal-text AA (4.5:1) on both dark and light backgrounds that neither the stability palette (yellow/red/gray/green/cyan) nor any theme intent claims. Verified by WCAG ratio computation; rendered live for visual review.
README tables adopt the same
[Cloud-only]notation, replacing the*suffix and legend entries — binary and docs now share one convention.Option-level and env-var scoped sections (e.g.
login's(Classic-only):options) are unchanged — a different, still-useful mechanism for constrained options on mixed commands.Test plan
tsc --noEmitclean;npm run checkclean (deadcollectCommandGroupsByScope/getSingleTypeScopeForCommand/CommandGroupDataremoved)\x1b[35m[Cloud-only]\x1b[0m);NO_COLOR/non-TTY renders plain🤖 Generated with Claude Code