Repository navigation
feat(cli): add project management commands - #1
Conversation
There was a problem hiding this comment.
Self-review of this exact head found no actionable issues. The complete CLI tree passed two clean snapshots at 15:09:23 and 15:14:34 KST, with staged/working/committed byte equality checks. All 86 compiled Node tests, typecheck, formatting, production dependency audit and npm archive installation pass. The installed gitdog executable, dog banner, key commands and 86-entry catalog run on Node 22.14. Regression tests cover Ctrl+C throughout login and concurrent desired activity commands. Real development E2E passed 39 CLI executions plus HTTP assertions, and removed fixture data and 39 unshared blobs with zero-data readback. This terminal-only change has verified command output and no website visual changes. The companion backend must be available before using the new operations.
Introduce the gitdog npm CLI with a dog ASCII banner, GitHub browser login, Firebase-style project initialization and aliases, automation configuration, tickets/actions, indexing, teams, invitations, account/billing commands and a generated catalog of 86 public operations.
Project API keys are saved only to private credential files; commands output metadata rather than secrets. Key-only requests never fall back to an owner session. The implementation includes strict callback/state checks, serialized refresh/logout, whole-login Ctrl+C cancellation and atomic desired-state project enable/disable.
Validation:
This is a terminal product; visual verification covers the ASCII banner and command output. Browser login exchanges and cancellation phases have real local HTTP regression coverage. No website UI is changed.
The npm package is prepared but is not published. The companion backend must be deployed before these project-key and desired-activity operations are used.
Companion backend: https://github.com/hyodotdev/gitdog.dev/pull/55