Closed heather999 closed 3 years ago
Thank you @heather999. It would be great if you could provide the PR with the workflow. I can create the PyPI API token and add it to the secrets. Shall I use any specific name for the secret? And should the secret name match the API token name?
I'll open a PR in a few minutes and add some comments to the workflow. You can use any name for the GitHub secret, it just needs to match what is used in the workflow. Some notes about the PyPI API tokens: https://pypi.org/help/#apitoken
Think we can consider this done. More updates will be coming to reorganize a bit, but we can handle that in a separate issue.
We can automate the upload to PyPI when
snmachine
is tagged and released here in GitHub. This will makesnmachine
pip installable without requiring manual intervention. While this workflow could be extended to do some testing, for now, we're just looking at setting up a simple workflow that is triggered whensnmachine
has a new release tag. Thanks to Eric Charles for supplying this workflow which is also documented here: https://www.caktusgroup.com/blog/2021/02/11/automating-pypi-releases/To make this work, the maintainer/developer indicated on the PyPI account for snmachine (like @Catarina-Alves !) would need to set up a PyPI API token and make it available here in GitHub using a secret. I'm happy to provide a PR with the workflow and help sort out the details.