Skip to content

ci: add release configuration for changelog generation#498

Merged
chenjiahan merged 2 commits intomainfrom
release_note_config_0310
Mar 10, 2026
Merged

ci: add release configuration for changelog generation#498
chenjiahan merged 2 commits intomainfrom
release_note_config_0310

Conversation

@chenjiahan
Copy link
Copy Markdown
Member

@chenjiahan chenjiahan commented Mar 10, 2026

Summary

Added .github/release.yml to define changelog categories and their corresponding labels for automated release notes.

Checklist

  • Tests updated (or not required).
  • Documentation updated (or not required).

@chenjiahan chenjiahan requested review from Copilot and fansenze March 10, 2026 02:36
@gemini-code-assist
Copy link
Copy Markdown

gemini-code-assist bot commented Mar 10, 2026

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new GitHub Actions configuration file (.github/release.yml) to standardize the generation of release notes. It defines various categories for changes, such as breaking changes, new features, and bug fixes, and maps them to specific GitHub labels. This setup ensures consistent and automated changelog creation for future releases, improving the clarity and efficiency of release communication.

Highlights

  • Release Configuration: Added a new configuration file, .github/release.yml, to define categories and their corresponding labels for automated changelog generation, streamlining the release process.
Changelog
  • .github/release.yml
    • Defined categories for changelog generation, including 'Breaking Changes', 'New Features', 'Performance', 'Bug Fixes', 'Refactor', 'Document', and 'Other Changes'.
    • Mapped each changelog category to specific GitHub labels (e.g., 'release: breaking change', 'release: feature').
Activity
  • No specific activity (comments, reviews, progress updates) was found in the provided context.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

@chenjiahan chenjiahan enabled auto-merge (squash) March 10, 2026 02:37
fansenze
fansenze previously approved these changes Mar 10, 2026
View reviewed changes
gemini-code-assist[bot]
gemini-code-assist bot reviewed Mar 10, 2026
View reviewed changes
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a .github/release.yml file to automate changelog generation. The configuration is well-defined. I have added a couple of suggestions to improve the consistency of labels and category titles for better long-term maintainability.

Copilot AI reviewed Mar 10, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a GitHub Releases configuration to standardize automated changelog generation based on PR labels, aligning release notes with the repo’s existing release label taxonomy.

Changes:

  • Introduced .github/release.yml defining changelog categories and their corresponding labels.
  • Added an “Other Changes” catch-all category for labeled/unlabeled items.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@chenjiahan
Update .github/release.yml
2cdb38e 
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@chenjiahan chenjiahan disabled auto-merge March 10, 2026 02:39
@chenjiahan chenjiahan merged commit 152b0f0 into main Mar 10, 2026
14 checks passed
@chenjiahan chenjiahan deleted the release_note_config_0310 branch March 10, 2026 03:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot Copilot left review comments

@fansenze fansenze fansenze approved these changes

+1 more reviewer

@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@chenjiahan @fansenze