flow init: add non-interactive flag for minimal setup
Open
Nobody has claimed this yet.
Improvement
- Dominant language
- Go
- Stars
- 209
- Forks
- 87
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 3
Description
Add non-interactive flag to flow init for minimal setup
Context
- Discussed in PR https://github.com/onflow/flow-cli/pull/2055
- Goal: enable CI and scripted init without prompts, accepting safe defaults
Proposal
- New flag:
--non-interactive(aliases:--yes,-y) - Behavior:
- Skip all prompts and use defaults for minimal project
- Do not open editors or interactive selectors
- Return non-zero exit on missing required inputs
Acceptance criteria
- Running
flow init --non-interactive .completes with no prompts - Minimal files created as with default choices
- Documented in help and README
Open questions
- Exact flag name and aliases
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the flow init command and review PR #2055 to understand the existing prompt and default paths. Resolve the open question about the flag name and aliases, then verify that non-interactive execution creates the minimal files, avoids prompts and editors, handles missing required inputs with a non-zero exit, and is documented in help and the README.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100