This repository has been archived by the owner on May 7, 2023. It is now read-only.
Restrict recursive inclusion filter #19
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
|
Oops! Thanks for noticing this. |
|
@jitseniesen, you should also run before doing a release, to remove all non-versioned files from the tree. |
|
@jitseniesen Please consider merging this and upload a follow-up release with a sane tarball. Thanks. |
|
@ghisvail Yes, I will (maybe not before the weekend though), Thanks for your advice. Same for @ccordoba12 . I updated my notes for the release process at https://github.com/spyder-ide/spyder-unittest/wiki/Release . If you have any comments, I'd be happy to hear them. |
|
@ghisvail I had some time today to upload 0.1.2 to PyPI with (hopefully) a corrected tar ball. |
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
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.
Otherwise, the upstream tarball may contain cache files (such as in the current tarball for version
0.1.1). A manual inspection of the tarball before upload would have prevented that mistake.