README coverage badge is a hardcoded 84% pointing at gocover.io
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4.7k
- Forks
- 258
- Avg merge
- 13h 31m
- Merged PRs (30d)
- 1
Description
The coverage badge in the README is a static shields.io image (coverage-84%25-brightgreen) that links to gocover.io, which has been gone for years. The number isn't current either: go test -cover . on main reports 75.0% today.
Happy to send a PR either way. Two options: drop the badge, or make it live. CI already runs go test -cover, so a live badge is a -coverprofile flag plus an upload step. Full disclosure, I build gocov (https://gocov.dev, source at https://github.com/gocov/gocov), an open-source coverage server, free for public repos. It needs no secret — uploads go through GitHub's OIDC token — but it does need the gocov GitHub App installed once on the account, so that part is your call. Which would you prefer?
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.
Research direction
Start with the coverage badge in README and inspect the existing CI command that runs go test -cover. Confirm with the maintainer whether the badge should be removed or made live; done means the README no longer points to the obsolete service and the displayed coverage is either absent or kept current.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100