ci(release): automate release notes format for GitHub releases#7
ci(release): automate release notes format for GitHub releases#7kantorcodes merged 1 commit intomainfrom
Conversation
Signed-off-by: Michael Kantor <6068672+kantorcodes@users.noreply.github.com>
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (1 files)
Reviewed by mimo-v2-pro-20260318 · 57,159 tokens |
There was a problem hiding this comment.
Code Review
This pull request introduces a .github/release.yml configuration file to automate changelog generation for GitHub releases. The configuration excludes specific labels and bots while categorizing changes into sections like Breaking Changes, Features, and Maintenance. Feedback suggests including the "test" label within the Maintenance category to align with the project's conventional commit types and alphabetizing the labels for better organization.
| - chore | ||
| - ci | ||
| - build | ||
| - refactor | ||
| - dependencies |
There was a problem hiding this comment.
Your CONTRIBUTING.md file lists test as a conventional commit type. To ensure test-related changes are categorized correctly in release notes, please add the test label to this 'Maintenance' category. For better readability and maintainability, I've also alphabetized the labels in the suggestion.
- build
- ci
- chore
- dependencies
- refactor
- test
This adds .github/release.yml so generated release notes are categorized and consistent for Go SDK releases.