Add codecov #920
Merged
Add codecov #920
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
natemort
requested review from
Groxx,
abhishekj720,
shijiesheng,
dkrotx,
taylanisikdemir and
demirkayaender
as code owners
natemort
force-pushed
the
codecov
branch
4 times, most recently
from
bd94ee1
to
ced5e62
Compare
Pull Request Test Coverage Report for Build 2522Details
💛 - Coveralls |
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. Thanks for integrating Codecov - We've got you covered ☂️ |
taylanisikdemir
approved these changes
Oct 12, 2024
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.
What changed?
Add a github workflow to run codecov to generate code coverage reports on pull requests.
Rather than running the tests directly we need to run them via docker to account for the thrift dependencies that are otherwise painful to set up.
Why?
Make it easier to track and enforce code coverage requirements.
How did you test it?
Creating this PR, hopefully it works.
Potential risks
Release notes
Documentation Changes