体验：kargo use 缺参不说看 current
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 0
- Avg merge
- 7d 23h
- Merged PRs (30d)
- 24
Description
用户路径
all-cli kargo use
报：
project name is required (or use --unset)
不说先看当前项目：all-cli kargo current。
kubectl/docker/glab/argocd 的 use 缺参已经指向 list。kargo 没有 list，入口是 current / status。
本轮不碰已有 issue：#54–#65。也不改正在改的 catalog / glab / argocd。
摩擦点
缺参时人不知道怎么发现当前 project。
建议改动
- 缺参错误补上
all-cli kargo current示例。
不在范围内
- 不改 glab/argocd use。
- 不 push、不开 PR、不 merge。
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 kargo use command's missing-argument handling and compare it with the existing kubectl, docker, glab, and argocd use guidance. Update the error to include an all-cli kargo current example, then run all-cli kargo use without a project name and confirm the guidance is shown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 85/100