Allow publish on test pypi workflow to fail#1177
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1177 +/- ##
=======================================
Coverage 78.30% 78.30%
=======================================
Files 84 84
Lines 9518 9518
Branches 775 775
=======================================
Hits 7453 7453
Misses 1879 1879
Partials 186 186 Continue to review full report at Codecov.
|
rytilahti
changed the title
Merged
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
2 participants
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.
A stop-gap solution to avoid all merges on master to fail just because a testpypi release already exists.
Something like https://github.com/pypa/setuptools_scm should probably used instead, and the real releases should be made on github releases and not on tags..