-
Notifications
You must be signed in to change notification settings - Fork 20
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
Support for Managing Existing Changelog File #5
Comments
Having the top header handling be a flag to configure the line would remove any awkward manual step necessary after releases to put the new header there in the first place and repeatedly dance around it.
|
This looks semi-related to #1 |
We would love to see this be implemented on Consul, Consul K8s and Consul API Gateway, since this would tremendously help visualize what is coming in an upcoming release prior to the release happening and a full changelog generated. |
Description
Currently,
changelog-build
covers the case of building a CHANGELOG section for a current release. It would be great if there was the ability to manage an existing CHANGELOG file to add that section.For example, the Terraform AWS Provider uses a script to build an updated CHANGELOG:
changelog-build
contentsIf this functionality would be acceptable for
changelog-build
, it would only need two additional pieces of optional information:References
https://github.com/hashicorp/terraform-provider-aws/blob/ad8293cc2ec8556783e4896eed33ae97e56f5919/scripts/generate-changelog.sh#L1-L54
The text was updated successfully, but these errors were encountered: