GitLab Service Badge tracking
- Dominant language
- JavaScript
- Stars
- 27.2k
- Forks
- 5.6k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 46
Description
## Purpose
Provide more GitLab badges and track the progress of these tasks. If you have other needs, please write them in the comments.
## Existing badges
- coverage
- license
- pipeline-status
- release
- tag
## Services Tracking list
- [x] contributors
- [ ] code size
- [ ] repo size
- [x] issue number(opened\closed\all)
- [x] merge requests number(opened\closed\all)
- [ ] milestone
- [ ] labels
- [x] forks
- [x] stars
- [x] language
- [x] last commit
- [ ] GitLab (`go.mod` \ `package.json` \ etc.) version
## References
- https://github.com/badges/shields/tree/master/services/gitlab
/cc @calebcartwright
Contributor guide
Research direction
Start by reviewing the existing implementations under services/gitlab and the referenced GitLab service directory. Compare the checked and unchecked items in the tracking list, then use the issue comments to determine which badge or badges are currently wanted. Done means the selected GitLab badge work is implemented with its coverage established by the project’s existing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100