-
Notifications
You must be signed in to change notification settings - Fork 2
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
Error on the Publish Python distribution to PyPI and TestPyPI Action #38
Comments
Additionnally, I can see that the current release on Github is 1.5.1 I thought the Action would automatically create a release on github along with publication on pypi, but that does not seem to be the case. |
Related to issue #38. We need to create a new release.
Yes! Good job! |
The workflow is creating a new release. The name of the release is copied from the name of the branch or tag that triggered the workflow. By my understanding, in order to avoid an error in future pull requests, we need to add a tag (on the branch you want to merge into OMG_master) if we want an automatic release on GitHub. I will try to add a line of code to skipt the GitHub-release job if the pull request does not have a tag. |
The last pull request #43 did not resolve this issue. But I am not sure if made a mistake in the order of the Git commands that I wrote i.e. the commit and the tag where made in different push. Maybe we have to commit, add a tag, and after that push to GitHub (and make a pull request). Would you like to try? For example: 1.- create a new branch, |
The "Sign the Python Distribution" job is returning the following error:
The text was updated successfully, but these errors were encountered: