Automate PyPI upload #82
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
DanielKotik
force-pushed
the
automate-pypi-upload
branch
from
3656cb2
to
1b6f32c
Compare
DanielKotik
force-pushed
the
automate-pypi-upload
branch
from
1b6f32c
to
a07ac1f
Compare
DanielKotik
force-pushed
the
automate-pypi-upload
branch
from
a07ac1f
to
ba3e391
Compare
DanielKotik
force-pushed
the
automate-pypi-upload
branch
from
ba3e391
to
24ffe02
Compare
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 adjusted the informations given in https://packaging.python.org/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/ and https://github.com/marketplace/actions/pypi-publish to our needs.
This workflow is triggered to upload a package distribution to PyPI for tagged commits on
masterand currently also for tagged commits ondevelop. The latter should change in an improved workflow (it doesn't matter for now since we won't tag commits ondevelop). The workflow also tries to publish to TestPyPI for every push onmasteranddevelop. This will hopefully ensure to get aware of any problems with regards to package building/publishing as early as possible.