Open
Conversation
Contributor
Author
|
I also added badges to the README, which will look nice once there is a version on pypi. See one of my repos for what these badges look like: https://github.com/Erotemic/xdoctest |
Collaborator
|
Pending chat on how to handle trusted publishing will move to merge. Thanks :D |
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
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.
Addresses #86
This adds the standard pypi publishing action integrated into github. To make this work the maintainers will need to take the following steps:
Ensure there is a PyPI account available to manage the
every-eval-everproject.Configure a Trusted Publisher for
every-eval-everon PyPI.every-eval-everevalevalevery_eval_everpublish.yamlpypiOptionally create/configure the pypi GitHub environment if you want environment protection rules. This is recommended, but not strictly required.
Once those steps are complete, creating and pushing a new version tag will both create the GitHub release and publish the package to PyPI.