-
-
Notifications
You must be signed in to change notification settings - Fork 737
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
Show code coverage #1223
Comments
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue and add a reference to this one if it’s related. Thank you! |
🎉 This issue has been resolved in version 10.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This still shows Unknown - I think because the Coveralls is drawing from the coverage-setup branch and not the master branch. I spent 15 minutes and still have no idea how to switch this. I also wasn't able to upload the coveralls via the npm script:
Any ideas? |
I investigated further and there is something odd ... I can reproduce when I run this locally using Coverall’s repo token
|
oh looks like when setting the I’ll try to set |
aaaaaand we are back in coverage business \o/ https://travis-ci.org/nock/nock/jobs/468705770 |
Yeah! Good work, Gregor! |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue and add a reference to this one if it’s related. Thank you! |
We have a coverage badge in our README but it currently shows "unknown". Let’s fix that, as discussed at #1202
The text was updated successfully, but these errors were encountered: