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.

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

feat: add code coverage to sanctions #27

Merged
merged 3 commits into from
Nov 21, 2023
Merged

Conversation

christopappas
Copy link
Contributor

Merge checklist:
Check off if complete or not applicable:

  • Documentation updated (not only docstrings)
  • Fixup commits are squashed away
  • Unit tests added/updated
  • Manual testing instructions provided
  • Noted any: Concerns, dependencies, migration issues, deadlines, tickets

Post-merge:

@christopappas christopappas requested a review from a team as a code owner November 20, 2023 19:25
Copy link

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 90%.
The branch rate is 69%.

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

requirements/ci.txt Outdated Show resolved Hide resolved
@christopappas christopappas merged commit 4babfd3 into main Nov 21, 2023
6 checks passed
@christopappas christopappas deleted the cpappas/REV-3777 branch November 21, 2023 18:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants