Automate the package naming in coveragerc #2198
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
…s don't have to do anything
|
👍 |
mdboom
added a commit
that referenced
this pull request
Mar 17, 2014
Automate the package naming in coveragerc
astrofrog
added a commit
to astrofrog/astropy-helpers
that referenced
this pull request
May 22, 2014
astrofrog
added a commit
to astrofrog/astropy-helpers
that referenced
this pull request
May 22, 2014
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.
This means that affiliated packages do not have to update their coveragerc, unless they want to customize it for any reason.
This is really just a refinement of the very recent change to enable coverage testing in affiliated packages in #2132 and astropy/package-template#39. This is required to enable astropy/package-template#41.