RFE: is it possible to start making github releases?🤔
kloczek opened this issue · 3 comments
On create github release entry is created email notification to those whom have set in your repo the web UI Watch->Releases.
gh release can contain additional comments (li changelog) or additional assets like release tar balls (by default it contains only assets from git tag) however all those part are not obligatory.
In simplest variant gh release can be empty because subiekt of the sent email contains git tag name.
I'm asking because my automation process uses those email notifications by trying to make preliminary automated upgrades of building packages, which allows saving some time on maintaining packaging procedures.
Probably other people may be interested to be instantly informed about release new version as well.
Documentation and examples of generate gh releases:
https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository
https://cli.github.com/manual/gh_release_upload/
jbms/sphinx-immaterial#282
https://github.com/marketplace/actions/github-release
https://pgjones.dev/blog/trusted-plublishing-2023/
jbms/sphinx-immaterial#281 (comment)
tox target to publish on pypi and make gh release https://github.com/jaraco/skeleton/blob/928e9a86d61d3a660948bcba7689f90216cc8243/tox.ini#L42-L58
Hi @klozcek, thanks for making this really good argument. I don't have any objections into adding GitHub Release. Especially if it's helpful for automation and watchers, which is something I had not previously really considered. I'll look into incorporating GitHub Release into the release process on the next release cycle.
@kloczek Rope 1.12.0 has just become the first release to use Github Release. Let me know if there is any further improvement that can be done for your use case!
Just checked my automation and it was able successfully process email notification about new release automatically updating my rpm package build procedure.
Thank you very much 👍 😄
Closing.