Conversation
3 similar comments
lasley
force-pushed
the
hotfix/coverage-ignore
branch
from
January 23, 2017 18:25
03c3229 to
6717936
Compare
Contributor
Author
|
I feel like maybe I did something wrong though, because there should have been a coverage raise here 😕 |
Contributor
Author
|
Hrm so whatever was dropping the coverage is fixed, because my PR now raised coverage. This is definitely not right & I don't know enough about coveragerc to make it right. All that in mind, closing. |
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.
I noticed a coverage drop when I edited the ReadMe in #8. This PR should fix that by providing an explicit includes for only python files in the package directory.