-
Notifications
You must be signed in to change notification settings - Fork 523
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
coverage badge #397
Comments
What service do you prefer? What about https://coveralls.io/? |
Note that we need to ask the TSC to add external services. I'm happy to use coveralls if somebody else set it up: unfortunately I have too many repos and my account cannot be opened anymore (that's also a good reason to not use them). |
Of course, thank you. I have seen that Node is using https://codecov.io/, maybe they would be more inclined to use that service? Or maybe there could be a way to just add a badge using Actions. |
I'm inclined to use codecov as well :). |
Sorry, you're right 😁 |
I have a working branch using codecov here. Is it safe to open a PR? |
Link to a report of the same branch: |
Nice! What would you need to enable this here? Could you just PR it? |
To enable just the coverage report with the badge I think it should work just by opening the PR. To enable the full integration it should be installed at the org level I think, but that can be done anytime, if necessary. The full integration should provide comments in PRs. |
I'll open a PR |
Would be nice to have a badge for coverage since we do often land stuff that does not maintain 100 coverage. I usually try to ensure 100 coverage just before a release.
The text was updated successfully, but these errors were encountered: