Update badges to put best foot forward. #247
Merged
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
|
Let me get the actual coverage report values - if I can. |
taras
approved these changes
Oct 23, 2018
1 similar comment
Links to public npm package and released version.
cowboyd
force-pushed
the
cl/badge-update
branch
from
ad3f9b7
to
c1e9622
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.
The coverage level is inaccurate, and reflects poorly on the project. In fact, we're not running coverage reports at all, and if we were, I have to imagine that the coverage level would be higher than 71%.
This change removes the coverage badge entirely until we actually commit to checking code coverage.
It also add adds an npm version badge so that it's clear which version is the current one.
Before
After
resolves #196