Bump codecov/codecov-action to v4 #378
Open
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #378 +/- ##
==========================================
+ Coverage 62.61% 69.49% +6.88%
==========================================
Files 27 25 -2
Lines 3838 3819 -19
==========================================
+ Hits 2403 2654 +251
+ Misses 1246 973 -273
- Partials 189 192 +3
Flags with carried forward coverage won't be shown. Click here to find out more. |
We need to use a token to upload coverage data. We can also disable coverage data search, as we already provide the list of files (a single file in our case) to include in the report. Signed-off-by: Antonin Bas <antonin.bas@broadcom.com>
antoninbas
force-pushed
the
bump-codecov/codecov-action-to-v4
branch
from
df59119
to
dd72ad0
Compare
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.
We need to use a token to upload coverage data.
We can also disable coverage data search, as we already provide the list of files (a single file in our case) to include in the report.