default completion command on "empty" project
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 44.6k
- Forks
- 3.5k
- PR merge metrics
- No merged PRs in 30d
Description
Running the default completion command right after cobra-init results in the root help being printed.
This can be confusing for newbies.
It would be helpful to add some hint that there is nothing to complete (either in the docs or in the command output).
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
Reproduce the behavior by running the default completion command immediately after cobra-init. Start at the completion command and the root-help path to determine where the empty-project case is handled. Done means the command no longer leaves newcomers with unexplained root help and instead provides a clear “nothing to complete” hint, either in output or documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100