You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On create github release entry is created email notificatio 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 nballs (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 subjest of the sent emial contais git tag name.
I'm aslking 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.
May I ask next time on release new version make the github release to have entry on https://github.com/jpirko/libteam/releases? 🤔
On create github release entry is created email notificatio 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 nballs (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 subjest of the sent emial contais git tag name.
I'm aslking 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.
Description about how to add create gh release using gh worflows jbms/sphinx-immaterial#281 (comment)
Other documentation:
https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository
https://github.com/marketplace/actions/github-release
https://pgjones.dev/blog/trusted-plublishing-2023/
The text was updated successfully, but these errors were encountered: