Skip to content
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?🤔 #1393

Closed
kloczek opened this issue Oct 23, 2023 · 1 comment
Closed

RFE: is it possible to start making github releases?🤔 #1393

kloczek opened this issue Oct 23, 2023 · 1 comment
Labels
duplicate The issue has been previously reported.

Comments

@kloczek
Copy link

kloczek commented Oct 23, 2023

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

@waylan
Copy link
Member

waylan commented Oct 24, 2023

This was added prior to the last release. Unfortunately due to an error parsing the release notes, the automation failed. A fix will be applied in #1388. I'm closing this as a duplicate.

@waylan waylan closed this as completed Oct 24, 2023
@waylan waylan added the duplicate The issue has been previously reported. label Oct 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate The issue has been previously reported.
Projects
None yet
Development

No branches or pull requests

2 participants