Add gh action for pypi publish #26
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
|
I did not, it it added now. |
|
@bpepple Want to try a release? |
@rkuykendall Sure, pushed v1.4.3 to PyPI. Worked without any issues, you just need to tag the release locally then push that tag to GH. |
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 gh action should work for publishing to PyPi when a new release is tagged. The only thing that might need your input is if you don't already have a PyPi Secret in the project setings. If you don't it's fairly straight-forward to setup:
If you don't already have an API token from pypi, you'll need to generate one. Info on that can be found here: https://pypi.org/help/#apitoken
Once you have that, head over to Setting->Secrets, and add the token with the name
PYPI_TOKEN.