You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
README badges: Travis CI and gocover.io are both dead #122
The README still shows a Travis CI badge (travis-ci.org shut down in 2021, CI is on GitHub Actions now) and a gocover.io coverage badge (gone for years), so both render broken.
Happy to send a PR. Swapping the Travis badge for the Actions one is trivial. For coverage there are two options: drop the badge, or wire one up. CI currently runs go test without -coverprofile, so it'd be an upload step in go.yml either way. Full disclosure, I build gocov (https://gocov.dev, source at https://github.com/gocov/gocov), an open-source coverage server, hosted free for public repos, but it needs one repo secret so that's your call. Which way do you want to go?
Small correction to what I wrote above: gocov no longer needs a repo secret. Uploads can go through GitHub's OIDC token (permissions: id-token: write) and the repo registers itself on the first upload; the only setup on your side would be a one-time install of the gocov GitHub App on the rs account. Opened #123 for the badge cleanup on its own; the coverage badge can be a separate follow-up if you want it.
Activity
bykclk commentedon Sep 4, 2026
Small correction to what I wrote above: gocov no longer needs a repo secret. Uploads can go through GitHub's OIDC token (
permissions: id-token: write) and the repo registers itself on the first upload; the only setup on your side would be a one-time install of the gocov GitHub App on thersaccount. Opened #123 for the badge cleanup on its own; the coverage badge can be a separate follow-up if you want it.README: replace the dead Travis CI and gocover.io badges (#123)