feat(ci): run test coverage in CI and upload to DeepSource #416
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
|
Here's the code health analysis summary for commits Analysis Summary
|
|
I need this merged pls |
lavafroth
approved these changes
Apr 13, 2024
|
Would this PR now make it so that the "DeepSource: Test coverage" check will work? |
|
@adhirajsinghchauhan see comments in PR body. It should, when the CI is triggered. Meaning if the CI is not triggered, the test will still fail sadly |
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.
Added a new job to CI which generates and uploads code coverage data to DeepSource automatically.
This will only run when .rs files are changed, so DeepSource will still fail test coverage on PRs not triggering the CI script.
We could extract it to a standalone Action, however I feel that's a waste of GitHub's resources.