Label Me Impressed
Breaking changes
The new coverage-label input namespaces PR comments and baseline artifacts per label (e.g., lcov-baseline-go instead of lcov-baseline). If you add a coverage-label to an existing invocation, it won't find the previous unlabeled baseline artifact — a fresh baseline will be created on the next push to your default branch. Any open PRs should be rebased or updated after that merge to pick up the new baseline.
Single-invocation users who don't use coverage-label are unaffected.
New: Multi-language coverage labels
The coverage-label input lets you run the action multiple times in the same workflow without PR comment or artifact collisions. Each label gets its own namespaced comment and baseline artifact.
- uses: pento/lcov-coverage-check@v3
with:
lcov-file: coverage/go.lcov
coverage-label: go
github-token: ${{ secrets.GITHUB_TOKEN }}
- uses: pento/lcov-coverage-check@v3
with:
lcov-file: coverage/frontend.lcov
coverage-label: frontend
github-token: ${{ secrets.GITHUB_TOKEN }}Smart collision detection warns when labels are inconsistently applied across runs. (#8)
Fix: PR comment pagination
The action now paginates the PR comment lookup, fixing duplicate comment posting on PRs with more than 100 comments. (#10)
Fix: Temp file cleanup
Temporary files created during LCOV filtering are now properly cleaned up. (#13)
Internal: Module restructuring
Split large script files into smaller, focused library modules under scripts/lib/. No user-facing changes. (#11)