Add GitHub Action to automatically publish pip package on new release #72
+19
−0
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
added 6 commits
February 17, 2023 13:58
… gh action for pip package creation
earonesty
reviewed
Mar 1, 2023
|
Any news on this? |
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 PR fixes #65
Is very important to always have an updated pip package that reflects the latest project release.
When a new release is created on the project (eg. 0.1.2) a pipeline starts and publish the new release on PyPI.org (thus updating the pip package).
Also added the pipeline status badge in the README.md (It will appear after the pipeline first run).
NOTE: in order for the pipeline to work, you need to add a secret named PYPI_API_TOKEN for the repo.
For reference take a look at my forked repo and the pip package published from my tests.
feel free to contact me for any clarification!