Add test coverage reporting with Codecov
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 394
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
Description
Add test coverage reporting to CI workflow using Codecov, similar to the liquid project's implementation.
Benefits
- Track test coverage trends over time
- Identify untested code paths
- Prevent coverage regressions in PRs
- Visualize coverage with badges
Implementation
Add a new coverage job to .github/workflows/go.yml that:
- Runs after tests pass
- Only runs on pushes (not PRs to avoid duplicate runs)
- Generates coverage report with
go test -coverprofile=coverage.out ./... - Uploads to Codecov using
codecov/codecov-action@v4 - Set
fail_ci_if_error: falseto not block on Codecov issues
Reference
See liquid project's coverage job: https://github.com/osteele/liquid/blob/main/.github/workflows/go.yml#L40-L66
Contributor guide
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 .github/workflows/go.yml and compare its existing test jobs with the linked liquid workflow. Verify the Go coverage command and Codecov action configuration, including push-only execution and non-blocking upload behavior. Done means the workflow produces coverage.out after tests pass and uploads it to Codecov without blocking CI on Codecov errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100