Merged
Conversation
Member
|
Can we setup a CI check that shows the current coverage, with codecov or something similar? |
Contributor
Author
|
Here is the current coverage report: https://app.codecov.io/gh/babel/babel-loader Can you install the codecov GitHub application to this repo? So the coverage should show up in checks. |
Member
Member
|
Oh, it also stopped reporting the coverage in the babel/babel repo since July 5th |
Contributor
Author
|
The coverage report now looks good to me: https://app.codecov.io/github/babel/babel-loader/commit/3ed721a5c2c0af04dbac02d3f40ce20adcba3ee5/tree/src
I have no idea why the codecov check is missing. Maybe the issue is on their sides. |
liuxingbaoyu
approved these changes
Jul 8, 2023
Member
|
Codecov is back :) |
This file contains hidden or 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
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.


Please Read the CONTRIBUTING Guidelines
In particular the portion on Commit Message Formatting
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
c8Does this PR introduce a breaking change?
Other information: Migrate to
c8, leveraging the v8 builtin coverage tools.