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
Publish release notes for services like sibbell.com? #739
Comments
I think a more pressing reason would be including the notes on the Releases page, rather than this specific tool. For example: It looks like the way to do this is through GitHub's UI: https://github.com/blog/1547-release-your-software and the notes aren't stored within Git itself, but on GitHub.
Some relevant discussion: olivierlacan/keep-a-changelog#1 Seems like a lot of work for a minor nice-to-have feature :/ What do you think @zavan (and others)? |
@zavan Hey, thanks for your suggestion. How does Sibbel work? By manual entry from us? |
@jodosha It fetches your GitHub faved repos and sends you an email when there's a new release/tag, in the email it sends the changes if they're on the GitHub release. Refer to @cllns for how to publish the changes. @cllns I agree that integrating this in the release process is too much work for a "nice to have", I'd just CTRL+C/CTRL+V the markdown from the CHANGELOG into the GitHub release, since they're not THAT frequent after all. |
@zavan Gotcha. Thank you.
This can work. |
We can try that for the next version. |
Okay, let's give it a shot. @AlfonsoUceda please take care of this. Closing this issue as "fixed". |
@AlfonsoUceda This is the page you need to add release notes: https://github.com/hanami/hanami/tags (have to switch to the 'Tags' tab, 'Releases' doesn't show any options for editing the release notes) |
@cllns thanks for the comment ;) |
Sibbel is a service that notifies devs about package updates:
It shows release notes in the email and website:
But not when they're not filled :(
So it would be nice if you could include release notes with the tags.
(I'm not affiliated to sibbel in any way)
The text was updated successfully, but these errors were encountered: