aanantaco/Cobertura + JUnit Coverage Report
Aggregate Cobertura coverage and JUnit test-result artifacts from every project in a repo into a single Markdown (or HTML) report for the GitHub Actions run, with optional regression detection against a baseline.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jul 10, 2026
- License
- MIT
Pinned Snippet
uses: aanantaco/coverage@ab3d55e91fd6563135cad00e2335520c8e0360cf # no releases — HEAD as of 2026-07-17tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| input | Directory containing coverage-*.xml and tests-*.xml artifacts. | yes | — |
| output | Output path. Use "-" for stdout, or $GITHUB_STEP_SUMMARY (default) to write to the run's Summary tab. | no | $GITHUB_STEP_SUMMARY |
| ignore | Path to a .coverageignore file (gitignore syntax). Optional. | no | "" |
| config | Path to coverage.yaml. Defaults to ./coverage.yaml if present. | no | "" |
| baseline | Path to a baseline coverage-summary.json for regression detection. | no | "" |
| fail-on-drop | Fail the job if total line coverage drops by more than this many percentage points. Leave empty to only annotate. | no | "" |
| emit-json | Also write a machine-readable coverage-summary.json to this path. | no | "" |
| go-version | Go version for the fallback build (used only when a prebuilt binary can't be downloaded, e.g. a loose ref instead of a full commit SHA). | no | 1.26 |
Outputs
no outputs