Skip to content

Replace Codecov with a coverage badge from the documentation site - #151

Merged
yawkat merged 3 commits into
mainfrom
claude/codecov-badge-alternatives-836530
Sep 25, 2026
Merged

yawkat merged 3 commits into
mainfrom
claude/codecov-badge-alternatives-836530

Conversation

@yawkat

@yawkat yawkat commented Sep 25, 2026 •

Copy link
Copy Markdown
Owner

Replaces the Codecov upload with a coverage badge and report hosted on the documentation site, so there are no third-party PR comments, status checks or app permissions.

  • scripts/jacoco_summary.py sums line coverage from the JaCoCo CSV report and can write a shields.io endpoint badge JSON.
  • The Linux amd64 test job writes the coverage summary to the job summary (visible on PRs). id-token: write is dropped.
  • The docs workflow runs the tests with -Pcoverage (needs the submodule and JDK 7 toolchain, like the test job), and just all publishes the JaCoCo HTML report and badge.json under current/coverage/.
  • The README coverage badge reads https://lz4-java.yawk.at/current/coverage/badge.json and links to the report.
  • On pages for older versions, the docs build pins the Maven Central badge to that page's version and drops the other badges, which only reflect the current state. Existing tags have no badges yet, so this only affects future releases.

Notes:

  • The badge updates on releases (or manual docs dispatches), not on every push to main. It is missing until the next docs deployment.
  • A test failure in the docs workflow now blocks the docs deployment.
  • The Codecov app / codecov.io project can be removed after merging.

🤖 Generated with Claude Code

Compute line coverage from the JaCoCo CSV report and show it in the job
summary instead of uploading it to Codecov. On pushes to main, a separate
job with contents: write publishes shields.io endpoint data to an orphan
badges branch, which the README badge reads.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@yawkat
yawkat enabled auto-merge (squash) September 25, 2026 18:29
@yawkat
yawkat disabled auto-merge September 25, 2026 18:37
Instead of pushing badge data to a badges branch on every push to main,
run the tests with coverage in the documentation build and publish the
JaCoCo report and badge data under current/coverage on the site. This
drops the job with contents: write and brings back a browsable report.

On pages for older versions, pin the Maven Central badge to that version
and drop the other badges, which only reflect the current state.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@yawkat yawkat changed the title Replace Codecov with a self-hosted coverage badge Replace Codecov with a coverage badge from the documentation site Sep 25, 2026
@yawkat
yawkat enabled auto-merge (squash) September 25, 2026 18:43
…alternatives-836530

# Conflicts:
#	docs/justfile
@yawkat
yawkat disabled auto-merge September 25, 2026 19:09
@yawkat
yawkat merged commit 58805dd into main Sep 25, 2026
3 checks passed
@yawkat
yawkat deleted the claude/codecov-badge-alternatives-836530 branch September 25, 2026 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant