-
Notifications
You must be signed in to change notification settings - Fork 12
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
Automatic PyPI upload on GitHub release #151
Conversation
This closes #110, right? |
Except for the docs tags (for which I've just added an RTD automation to auto-activate version tags). It does mean you should create new package releases via a GitHub release rather than pushing a tag though. |
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.
LGTM
@angus-g, merge? |
I'll just do one quick test, then I'll merge! |
take your time! |
Releases marked as "prerelease" will go to TestPyPI, for workflow testing, etc.
This will fill out the PyPI project page, and also prevent an error during the check phase of the packaging workflow.
86f32a8
to
b80207e
Compare
Alright, figured out that we need the |
Should do, yeah. |
Releases marked as "prerelease" will go to TestPyPI, for workflow testing, etc. Just as an option for #110, probably good to get @dougiesquire's feedback.