-
Notifications
You must be signed in to change notification settings - Fork 377
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
Adding 'go' as the release type makes changes to 'CHANGES.md' instead of CHANGELOG.md #924
Comments
It also seems like the go release-type creates CHANGES.md instead of updating an existing CHANGELOG.md. Is there any way to override this behaviour? It seems like setting the I am NOT able to override this behavior even after setting up the releaseType: go
handleGHRelease: true
changelogPath: CHANGELOG.md |
@codyoss is it common for go to use CHANGES.md rather than CHANGELOG.md? or was this design decision specific to how we were doing things on our team? |
@bcoe CHANGES was a pre-existing pattern that our teams Go libraries had used. I think in general CHANGELOG is more prevalent, but even then I don't actually see most projects use them as they seem to just favor using Github releases. |
@codyoss I think we use |
@codyoss Yup, we are fully migrated. That sounds good to me! |
Any update on this? Would be great if the |
🤖 I have created a release \*beep\* \*boop\* --- ## [11.18.0](https://www.github.com/googleapis/release-please/compare/v11.17.0...v11.18.0) (2021-07-28) ### Features * **go:** default to CHANGELOG.md ([#986](https://www.github.com/googleapis/release-please/issues/986)) ([5ab2069](https://www.github.com/googleapis/release-please/commit/5ab2069c22f3b5d5aba9dbd34f061a4de871e07c)), closes [#924](https://www.github.com/googleapis/release-please/issues/924) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
@abemedia @atreya2011 this should be working now 👍 sorry it took a little while to get to. |
Awesome, thanks! |
Thank you 🙏🏼 |
#890
I noticed a recent pull request adds a generic go release type and the documentation is not up to date to reflect the same.
The text was updated successfully, but these errors were encountered: