Repository navigation
feat: add per-severity counts to the code issues badge JSON - #72
Merged
Merged
Conversation
codecheckToolbox now writes the error, warning and info counts to a "counts" field in code_issues.json, so matbox-actions can draw one badge segment per severity. The label, message and color fields are unchanged, so renderers that ignore the counts still draw the current single badge. writeBadgeJSONFile and the internal createBadge take an optional Counts name-value argument. The field is omitted when Counts is empty, which keeps every other badge JSON unchanged. The legacy pybadges SVG fallback ignores the counts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Test Results37 tests 37 ✅ 31s ⏱️ Results for commit e7c78b8. ♻️ This comment has been updated with latest results. |
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
1 participant
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.
codecheckToolboxwrites the code issues badge asdocs/reports/badges/code_issues.jsonwithlabel,messageandcolor, and matbox-actions renders that file to.github/badges/code_issues.svg. This adds acountsfield with the error, warning and info counts, so matbox-actions can draw one badge segment per severity (ehennestad/matbox-actions#26).The
label,messageandcolorfields are unchanged. matbox-actions versions that ignorecountskeep rendering the current single badge.writeBadgeJSONFileand the internalcreateBadgetake an optionalCountsname-value argument. The field is written only whenCountsis given, so the tests badge and the "tested with" badge JSON are unchanged. The legacy pybadges SVG fallback ignores the counts.TasksTestchecks that the counts are present and add up to the total in the message, and thatwriteBadgeJSONFileomits the field by default.🤖 Generated with Claude Code