Issues labels
Open
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Hello,
I think you should use issues label to create categories and make contribution easier to GitHub users.
For example, I would be glad to contribute to keybase/client but it is hard to find issues to resolve when there are no labels.
Contributor guide
No contributing guide indexed for this repository
Research direction
No source file or test is identified. Start by reviewing the repository’s open issues and current GitHub label setup, then define a workable category scheme and apply it consistently so contributors can find issues by category.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100