Open
Conversation
Add MishaKav/pytest-coverage-comment action to post code coverage summary as a PR comment. Changes include: - Add pull-requests: write permission - Add --junitxml=pytest.xml flag for test summary - Add coverage comment step with per-file breakdown Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
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.
Add MishaKav/pytest-coverage-comment action to post code coverage summary as a PR comment. Changes include:
Purpose
This pull request updates the GitHub Actions workflow to improve test reporting for pull requests. The main changes are the addition of automated coverage comments on pull requests and updates to permissions to support this feature.
CI workflow improvements:
pull-requests: writepermission to the workflow to allow posting comments on pull requests.MishaKav/pytest-coverage-commentGitHub Action, which posts test coverage summaries as comments on pull requests. This step is conditionally executed only for non-fork pull requests and when backend tests are not skipped.junitxmlreport (pytest.xml), which is required as input for the coverage comment action.Does this introduce a breaking change?