-
-
Notifications
You must be signed in to change notification settings - Fork 513
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
CHANGELOG.md content for release notes #662
Comments
I wrote a plugin:
Save it as
|
That's awesome, @eMarek! There is https://www.npmjs.com/package/@semabit/release-it-bump-keepachangelog but it seems unmaintained. The current solutions offered by release-it and/or plugins are all based on the Git commit history (basically I think your plugin is very useful. I'm sure you are not the only one keeping a changelog like this! Maybe you want to publish your plugin (github/npm)? I'm happy to take over the idea and move it to e.g. |
Yes, please move it to |
I've released https://github.com/release-it/keep-a-changelog. Please let me know what you think, how it works! |
Looks good. Thanks! |
I am reading change log docs and usage examples with
release-it
package. Maybe I don't understand it well enough or maybe the way I use change log is a bit different then others.My workflow is next. I am following the "rules" of Keep a Changelog. During the process of development we (I and my team) manually update the CHANGELOG.md file. I really don't want to have commit logs inside there. Many times commit logs from different developers are just a pure trash. That's why I prefer to have manual entries in CHANGLOG.md file. This way even project managers are able to understand them. Commit logs are too technically deep for them. Okay anyway. Right before a release our CHANGLOG.md file looks something like this (an example):
As you can see my release notes are already prepared when I am making a new release and I want to use them. Actually, to be more precise I would love to have 2 things:
## [Unreleased]
text to be replaced with## [5.7.0] - 2020-05-05
(so new releasing version and today's date) and committed and pushed alongside with releasing new version.Is this possible to achieve this workflow with
release-it
package or not?The text was updated successfully, but these errors were encountered: