Add CLI option so that the tool can be run without first creating a configuration file
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
Research direction
Start by locating the Go CLI option parsing and the configuration-file setup. Add support for providing -repo=owner/repo multiple times so the tool runs without a configuration file, then verify that each repository is accepted and the normal CLI checks pass.
Written by the indexing model from the issue text.
Description
Add option -repo=owner/repo that can be provided multiple times
- Dominant language
- Go
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from azavea/github-labeller
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
azavea/github-labeller#13 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
azavea/github-labeller#11 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
azavea/github-labeller#10 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in azavea/github-labeller
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100