-
Notifications
You must be signed in to change notification settings - Fork 34
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
Use GitHub releases #226
Comments
Or delete all existing releases? And then the github repos main page will just says "123 tags", instead of showing an old release. |
We could, but I think we should embrace releases :) We are embracing issues and discussions, so using releases makes sense to me! |
I don't get how to use the annotated tag message as body for the release, and others seems to have the same problem too: actions/create-release#118 |
And |
but maybe |
Creates a GH release, but in draft mode because the current action can't get the git tag message as body. Closes #226
@carlhoerberg what about
Found it in https://stackoverflow.com/questions/5358336/how-to-list-all-tags-along-with-the-full-message-in-git |
Could also do (I'm sure there's a clever way to remove the PGP block)
|
Creates a GH release, but in draft mode because the current action can't get the git tag message as body. Closes #226
Uses the annotated tag body as part of release notes. Also adds a diff link against the previous version to the release notes. Closes #226 Co-authored-by: Patrik Ragnarsson <[email protected]>
We can use https://github.com/marketplace/actions/create-a-release
Upside: "Releases" are more prominent displayed in the GitHub UI (e.g. in the side bar on the repo front page https://github.com/cloudamqp/avalanchemq)
Originally posted by @carlhoerberg in #219 (comment)
The text was updated successfully, but these errors were encountered: