-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add workflow-template for publishing Python project to PyPI #4
Conversation
Primarily inspired by the work on omero-cli-zarr this should make the standard publish to PyPI on tags workflow activatable at minimal cost across projects.
Good to have beaten on this a bit via ome/omero-cli-zarr#37 and ome/omero-cli-zarr#41 😉 |
Also including ome/omero-cli-zarr@ec0bebd in the history. Short version: this all started as an honorable attempt to create a template workflow implementing https://packaging.python.org/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/#publishing-the-distribution-to-pypi-and-testpypi but in practice ended up with a more simple but effective publishing of tags to PyPi. |
Maybe a file like REFERENCES.md could be useful to capture link https://packaging.python.org/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/#publishing-the-distribution-to-pypi-and-testpypi in case one would like for example to use testpypi |
Would this file be stored under |
I don't have any example. I was thinking that it could be alongside of the readme and other files |
Pushed f41ca70 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for capturing the reference
Primarily inspired by the work on omero-cli-zarr this should make the standard publish to PyPI on tags workflow activatable at minimal cost across projects.
/cc @ome/python