Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feat: add coverage comments to PRs #379

Merged
merged 2 commits into from
Dec 6, 2023
Merged

Feat: add coverage comments to PRs #379

merged 2 commits into from
Dec 6, 2023

Conversation

thekaveman
Copy link
Member

Closes #301

@thekaveman thekaveman self-assigned this Dec 5, 2023
@thekaveman thekaveman requested a review from a team as a code owner December 5, 2023 17:59
@github-actions GitHub Actions
Copy link

github-actions bot commented Dec 5, 2023

Coverage report

Note

Coverage data for the default branch was not found.
This usually happens when the action has not run on the default
branch yet, for example right after deploying it into the workflows.

The coverage rate is 82.31%.
The branch rate is 80%.

None of the new lines are part of the tested code. Therefore, there is no coverage data about them.

@thekaveman thekaveman merged commit 2cf865c into dev Dec 6, 2023
8 checks passed
@thekaveman thekaveman deleted the feat/coverage branch December 6, 2023 21:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@machikoyasuda machikoyasuda machikoyasuda approved these changes

Assignees

@thekaveman thekaveman

Labels
None yet
Projects
None yet
Milestone
Code cleanup and stabilization
Development

Successfully merging this pull request may close these issues.

Incorporate coverage diff reporting
2 participants
@thekaveman @machikoyasuda