Interactive, arrow-key guided setup for whygraph init#32
Merged
Conversation
Prompts for the agent, analyze/rationale LLMs (+ per-provider API keys), and the source-control provider (+ token), shows a secret-masked summary panel to confirm, then writes both whygraph.example.toml (no secrets) and a ready-to-run whygraph.toml. --yes and any non-TTY invocation skip all prompts and preserve today's behavior.
CI checks ruff format --check in addition to ruff check, which wasn't run before the last push. Reformat the affected files and add a "Before pushing" section to CLAUDE.md spelling out all three commands CI gates on, so this doesn't happen again.
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
whygraph initon a terminal now runs a create-next-app-style guided setup: agent, analyze/rationale LLM provider+model (+ per-provider API key), and source-control provider (+ GitHub token) — every prompt defaulted so a bare Enter accepts it.set (hidden)/from $ENV/not set, never a value), gated by a final "Write these files?" confirm.whygraph.example.toml(no secrets) and a ready-to-runwhygraph.toml(with any secrets entered), from one parameterized template rendered two ways.--yes/-y(and any non-TTY invocation — pipes, CI, git hooks) skips all prompts, uses defaults, and never clobbers an existingwhygraph.toml— identical to prior behavior.Test plan
uv run pytest— 518 passedruff check src/ tests/— cleantests/fixtures/default_config_golden.toml) pins byte-exact reproduction of the unfilled templatewhygraph init --yesin a scratch repo writes both files with defaults, preserves an existingwhygraph.toml