ci: give reviewers visibility into coverage impact before merge#58
Merged
Conversation
Coverage Report
|
||||||||||||||||||||
benner
force-pushed
the
ci/add-pr-coverage-report
branch
2 times, most recently
from
4f36c46 to
e3ea57a
Compare
Adds XML report generation and a PR comment showing current coverage per file via MishaKav/pytest-coverage-comment@v1.7.2 (SHA-pinned). Signed-off-by: Nerijus Bendžiūnas <nerijus.bendziunas@gmail.com>
benner
force-pushed
the
ci/add-pr-coverage-report
branch
from
e3ea57a to
b5a81c4
Compare
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.
Adds XML report generation and a PR comment showing current coverage
per file via MishaKav/pytest-coverage-comment@v1.7.2 (SHA-pinned).