Skip to content
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

Closed
atreya2011 opened this issue Jun 5, 2021 · 9 comments · Fixed by #986
Closed
Assignees
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@atreya2011
Copy link

atreya2011 commented Jun 5, 2021

#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.

@yoshi-automation yoshi-automation added the triage me I really want to be triaged. label Jun 6, 2021
@atreya2011
Copy link
Author

atreya2011 commented Jun 7, 2021

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 changelog-path in the release-please-action does not seem to override this behaviour...

I am NOT able to override this behavior even after setting up the release-please bot with the following release-please.yml

releaseType: go
handleGHRelease: true
changelogPath: CHANGELOG.md

@sofisl sofisl changed the title Add 'go' to release types list in README.md Adding 'go' as the release type makes changes to 'CHANGES.md' instead of CHANGELOG.md Jun 7, 2021
@sofisl sofisl added priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Jun 7, 2021
@bcoe bcoe removed the triage me I really want to be triaged. label Jun 7, 2021
@bcoe
Copy link
Contributor

bcoe commented Jun 7, 2021

@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?

@codyoss
Copy link
Member

codyoss commented Jun 8, 2021

@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.

@bcoe
Copy link
Contributor

bcoe commented Jun 8, 2021

@codyoss I think we use go-yoshi everywhere for our internal stuff now? wondering if we could make the go releaser use CHANGELOG, and address @atreya2011's hiccup.

@codyoss
Copy link
Member

codyoss commented Jun 8, 2021

@codyoss Yup, we are fully migrated. That sounds good to me!

@abemedia
Copy link
Contributor

Any update on this? Would be great if the changelogPath option actually worked but even just changing the go releaser to CHANGELOG.md would already be good!

bcoe added a commit to googleapis/release-please-action that referenced this issue Jul 28, 2021
bcoe added a commit that referenced this issue Jul 28, 2021
@bcoe bcoe closed this as completed in #986 Jul 28, 2021
bcoe added a commit that referenced this issue Jul 28, 2021
bcoe added a commit to googleapis/release-please-action that referenced this issue Jul 28, 2021
@bcoe
Copy link
Contributor

bcoe commented Jul 28, 2021

@abemedia @atreya2011 this should be working now 👍 sorry it took a little while to get to.

@abemedia
Copy link
Contributor

Awesome, thanks!

@atreya2011
Copy link
Author

Thank you 🙏🏼

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants
@bcoe @abemedia @codyoss @atreya2011 @yoshi-automation @sofisl and others