Repository navigation
CI: publish a self-hosted coverage badge to gh-pages - #204
Merged
Merged
Conversation
On pushes to main, a new coverage-badge job takes the gate total from the Go Coverage Gate job and commits badges/coverage.json to gh-pages in the shields.io endpoint format. Green at 80% or above, yellow at 60% or above, red otherwise. No external coverage service or token. README gets the matching shields.io endpoint badge.
PaxMachinaOne
approved these changes
Oct 17, 2026
This was referenced Oct 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a coverage badge that CI generates itself, with no outside coverage service and no tokens. Based on main after #203.
Go Coverage Gatejob now exposes the gate total (fromcoverage.outviago tool cover -func) as a job output.coverage-badgejob runs only on pushes to main, withcontents: write. It checks outgh-pages, writesbadges/coverage.jsonin the shields.io endpoint format (brightgreen at 80% or above, yellow at 60% or above, red otherwise) and pushes it as a normal commit. If the value has not changed it skips the commit, and it retries with a rebase if gh-pages moved during the push.https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/KafScale/platform/gh-pages/badges/coverage.json, linking to the CI workflow.The badge shows a number after the first main run once this merges.
Checks:
actionlintclean, license headers pass.