Repository navigation
Enable the CLI setup flow on main - #11
Draft
frances720 wants to merge 1 commit into
Draft
frances720 wants to merge 1 commit into
frances720 wants to merge 1 commit into
Conversation
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.
promptless setuponmaincurrently prints “not available yet” and exits. This enables the full setup flow: sign in or create an account, connect GitHub, select documentation and source repositories, review the proposed configuration before applying it, complete onboarding, and optionally backfill recent pull requests.The existing implementation from #10 was merged into
setup-command-groundwork, leavingmainwith its placeholder. This brings that implementation ontomain, updates shell completion and usage documentation, and adds two fixes:setup_unavailablewhen the server lacks the setup status route, instead of exposing an unexplained 404. Specific organization-not-found responses retain their original error.Validation: typecheck and build pass; all 127 tests pass. New integration tests exercise the real encrypted loopback callback and identity API against a local fixture, including successful signup handoff, wrong-organization credentials, rejected credentials, and cancellation. Built-binary checks verify help, invalid arguments, and non-interactive use. Four terminal walkthroughs against a local fake runtime verify confirmed configuration application, cancellation before writes, a completed rerun with no writes, and the missing-backend error.
Release dependencies: deploy the backend stack before releasing this CLI: new-user organization creation (Promptless/promptless#5358), trial enforcement (Promptless/promptless#5359), setup routes (Promptless/promptless#5372), cardless trial completion (Promptless/promptless#5373), and optional backfill key authentication (Promptless/promptless#5371). The production setup-status probe currently returns 404. No real account, GitHub installation, config, or trial was created during validation. npm publication and a production walkthrough remain outstanding.