-
Notifications
You must be signed in to change notification settings - Fork 15
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
RFE: is it possible to start making github releases?🤔 #46
Comments
Hi @kloczek I have added a tag-only GitHub release for 5.0.4 just now at https://github.com/hsluv/hsluv-python/releases/tag/v5.0.4 . Regarding automation ofr creation of GitHub releases, I don't see much value in that personally, so I won't be the one to build that or compaign for it. Regarding release notification, I use rss2email and the RSS feed of Repology to be notified of new releases of software I maintain even without GitHub releases. The repology page of hsluv-python is https://repology.org/project/python:hsluv/versions . I'm unsure why Fedora is not listed there, could be a naming-difference thing. Repology works great, it helps me be a better Gentoo maintainer. @boronine shall we close this as fixed? |
Yes if you will remember to add gh release entry on next release 😋 |
@kloczek that was the plan at least, yes 😃 |
Seems complete, closing… |
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
The text was updated successfully, but these errors were encountered: