Add statement coverage into tabulate #8
Merged
Conversation
This file contains 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
fungilation
reviewed
Jan 24, 2021
There was a problem hiding this comment.
This is great! I'm switching my repos' test coverage CI bot to this, from https://github.com/mattallty/jest-github-action. Simply better output, while also less space consuming with table collapsed and show only total coverage % by default.
Great enough that I'm switching even though this CI bot doesn't have test failure annotations like jest-github-action does. Thanks for this action @romeovs 👏🏼
romeovs
requested changes
Feb 12, 2021
jussikinnula
force-pushed
the
add-statement-coverage
branch
from
61b6e49
to
1648857
Compare
romeovs
approved these changes
Feb 13, 2021
klausbadelt
pushed a commit
to klausbadelt/lcov-reporter-action
that referenced
this pull request
Mar 5, 2023
…tion Remove summary title too if the table is empty.
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.
I wanted to make the comment match the same format as is produced by
clover.xmlandlcov.inforeport producing tools. So basically adding statement coverage into comment.Preview