fix: Don't run publishing workflow on tags to avoid errors #45
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.
With the old workflow if the publishing workflow was run after a new tag was created
no release would get published to TestPyPI as the workflow that would get kicked off from the
push
event tomaster
(and so NOT atag
event) would fail the "Verify untagged commits have dev versions" steppylhe/.github/workflows/publish-package.yml
Lines 37 to 47 in dd781b7
as it would
pylhe/.github/workflows/publish-package.yml
Line 38 in dd781b7
but then also
"${wheel_name}" != *"dev"*
given that it comes from a tag. So nothing gets published.Similarly, the workflow that would get kicked off from the
tag
event will just run though but will passpylhe/.github/workflows/publish-package.yml
Lines 61 to 67 in dd781b7
as it is has
github.ref
of'refs/tags/'
and so nothing happens at all.This PR fixes that by just letting pushes to
master
publish to TestPyPI and then letting the releases publish to PyPI.