RFE: is it possible to start making github releases?🤔
kloczek opened this issue · 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
Hello,
Creating GitHub releases is not planned at the moment, simply because they are not needed: all the required files are in the source code (i.e. we do not provide compiled files).
About your use-case, have you tried subscribing to GitHub tags? We do publish tags upon new releases.
Again: this RFE has nothing to do with any files.
By create gh release is spread email notification about new release.
You don't need even add comment to to gh release because new release notification is autogenerated out of git tag name.
There is no such things like subscribing tonew git tags.