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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFE: is it possible to start making github releases?馃 #1400

Open
kloczek opened this issue Feb 23, 2024 · 3 comments
Open

RFE: is it possible to start making github releases?馃 #1400

kloczek opened this issue Feb 23, 2024 · 3 comments

Comments

@kloczek
Copy link

kloczek commented Feb 23, 2024

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

@rubyFeedback
Copy link

rubyFeedback commented Mar 15, 2024

I agree with this, even though I come to this conclusion from another point of view - but also because when
"official" releases are made, it helps ensure a certain quality (e. g. stable releases tend to work better than
shifting git-based releases in general, that was my experience at the least). Perhaps something that seems
reasonable, twice per year or perhaps even four times per year for stable releases.

@kloczek
Copy link
Author

kloczek commented Mar 15, 2024

No, no .. this RFE is not about frequency of the releases but about make github releases on tagging code which adds entries to https://github.com/google/shaderc/releases (which is still empty here 馃構 )

@kloczek
Copy link
Author

kloczek commented Mar 15, 2024

On create that entry automatically is send email notification to those who have set Watch -> Custom -> Release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants