-
Notifications
You must be signed in to change notification settings - Fork 48
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
Maintain a changelog #7
Comments
@JasonEtco added in probot/template#4 (comment): Might also be worth looking into how semantic-release does this. Setting it up is a bit of a mystery to me, but I like their convention of prefixing commits with certain keywords, then organizing the resulting release post by those keywords. So:
|
This might be related, although I haven't yet looked through the code to figure out what it actually does. But it seems likely to do something like this: https://github.com/uber-workflow/probot-app-release-notes
Ah, after some perusal it looks like |
I made https://github.com/mikz/probot-changelog It does not check any specific format, just that changelog changed.
|
Hi, I have created a github app to maintain changelog: PRCLbot It currently follows the format of keepachangelog Landing Page: PRCLbot It also has additional features like
|
This looks really cool @mukul13! |
Via @benbalter in probot/probot#15
When a pull request is merged, add a line to
CHANGELOG.md
orHISTORY.md
, with the PR title, number, and if the contributor is not a maintainer, give them props, optionally categorizing the updates based on tags.@jekyllbot does this (with a slightly different behavior that I don't like), but the end result could look somethign like this:
The text was updated successfully, but these errors were encountered: