-
Notifications
You must be signed in to change notification settings - Fork 274
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
Automatically create a release on github #894
Comments
We could do this with entrypoints, see https://zestreleaser.readthedocs.io/en/latest/entrypoints.html. I'm not sure it's worth it, though. I'd rather keep the process manual and not have to maintain some code for this. |
I'm surprised that zest doesn't support this out-of-the-box. Also, there's the question of converting the RST format from the changelog into markdown... |
We could use pandoc, but it's a big dependency.
|
See #893 (comment) |
Everything is now using Markdown. I believe cutting a new release on Github should be as simple as hitting a specific API endpoint? Or we could take it the other way : https://www.caktusgroup.com/blog/2021/02/11/automating-pypi-releases/ |
Here is the API we should use |
I believe you could do a lot of things with GHA, for instance release on push can create a github release based on events like pushing, it can also build release notes for github, and publish a tag on the release commit. The action can be triggered with labels on the release PR. |
That would indeed make our life much easier. |
We use zest for the release process: https://ihatemoney.readthedocs.io/en/latest/contributing.html#how-to-release
It would be nice if zest could automatically create a release on github with the changelog extract.
The text was updated successfully, but these errors were encountered: