chore: update score_tooling to 2.2.0 - #390
Merged
Merged
Conversation
Pure feature release: the coverage report generator now emits a markdown job summary. No repo-side changes needed — inside GitHub Actions the existing coverage workflow picks it up automatically via GITHUB_STEP_SUMMARY (overall line/branch/file tables, per-directory rollup, least-covered and exact-0% file lists on the run page). Validated locally against the registry release: 3/3 tests, coverage unchanged (86.95% lines / 90.74% branches effective), summary rendered.
dcalavrezo-qorix
requested review from
PandaeDo,
antonkri,
umaucher and
vinodreddy-g
as code owners
August 24, 2026 11:51
License Check Results🚀 The license check job ran with the Bazel command: bazel run --lockfile_mode=error //:license-checkStatus: Click to expand output |
|
The created documentation from the pull request is available at: docu-html |
umaucher
approved these changes
Aug 24, 2026
PandaeDo
requested a deployment
to
workflow-approval
August 24, 2026 17:24 — with
GitHub Actions
Waiting
PandaeDo
requested a deployment
to
workflow-approval
August 24, 2026 17:24 — with
GitHub Actions
Waiting
PandaeDo
approved these changes
Aug 24, 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
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.
Pure feature bump: score_tooling 2.2.0's coverage report generator emits a markdown job summary (tooling#440).
No workflow changes needed — the existing
llvm_coveragejob picks it up automatically viaGITHUB_STEP_SUMMARY. After this merges, every coverage run shows on its run page: overall line/branch/file tables with progress bars, raw-vs-effective (justifications), a per-directory rollup (worst first), and collapsible least-covered / exact-0% file lists.Validated locally against the registry release: 3/3 tests, coverage unchanged (86.95% lines / 90.74% branches effective), summary rendered from this repo's real data. The
llvm_coveragecheck of THIS PR will demonstrate it live — expand the job summary on the run page.