chore: message type detection in release notes script

[UnschooledGamer]

updates the Release notes script to pick up scoped commits (i.e feat(plugin)), instead of ignoring them

[gemini-code-assist]

Summary of Changes

Hello @UnschooledGamer, I'm Gemini Code Assist¹! 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 refines the commit message parsing within the release notes generation script. It ensures that commit messages following the conventional commit format, specifically those including a scope (e.g., feat(plugin):), are correctly categorized, preventing them from being overlooked during release note generation.

Highlights

• Improved Commit Type Detection: The release notes script now correctly identifies commit types that include a scope, such as feat(plugin):.
• Enhanced categorizeCommits Function: The logic within the categorizeCommits function has been updated to parse commit messages more robustly, preventing scoped commits from being miscategorized.

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

[UnschooledGamer]

Who asked Gemini to review ahhh? it's just a small change lol.

[gemini-code-assist]

Code Review

This pull request updates the release notes generation script to correctly categorize commits that use a scope in their type, such as feat(plugin): .... The change is a good improvement for handling more diverse commit message formats. My review includes a suggestion to simplify the detection logic by removing redundant checks and using a regular expression, which would improve maintainability and clarity.