replace custom coverage action with py-cov-comment #113
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
LGro
force-pushed
the
feature/python-coverage-comment-action
branch
5 times, most recently
from
2f6e9e5 to
7690eb7
Compare
Coverage report
The coverage rate is None of the new lines are part of the tested code. Therefore, there is no coverage data about them. |
Signed-off-by: Grossberger Lukas (CR/AIR2.2) <Lukas.Grossberger@de.bosch.com>
LGro
force-pushed
the
feature/python-coverage-comment-action
branch
from
7690eb7 to
249db77
Compare
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.
Our self made coverage reporting wasn't only causing failing tests to slip (#111) but also hid the errors when they occurred. So here is an attempt to switch to https://github.com/marketplace/actions/python-coverage-comment as recommended by @dynobo.