ci: Convert Conventional Commits and Release Please to GitHub Actions

[holtskinner]

Google GitHub Apps will be shut down

[gemini-code-assist]

Summary of Changes

Hello @holtskinner, 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!

I am migrating the repository's continuous integration and release management processes from Google GitHub Apps to native GitHub Actions. This change is necessitated by the upcoming shutdown of Google GitHub Apps. The primary impact of this pull request is the removal of old configuration files related to conventional commit linting and Release Please, paving the way for new GitHub Actions workflows to be implemented in subsequent changes.

Highlights

• Removed Conventional Commit Linting Configuration: I have removed the .github/conventional-commit-lint.yaml file, which previously configured conventional commit linting. This removal is part of the migration to GitHub Actions for handling commit validation.
• Removed Release Please Configuration: I have removed the .github/release-please.yml file, which contained the configuration for the Release Please GitHub App. This change is necessary as the project transitions to using GitHub Actions for release management.
• Removed Release Trigger Configuration: I have removed the .github/release-trigger.yml file, which was used to enable release triggers. This is part of the broader effort to consolidate CI/CD processes under GitHub Actions.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 or fill out our survey to provide feedback.

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

[gemini-code-assist]

Code Review

This pull request aims to migrate from the deprecated Google GitHub Apps for Conventional Commits and Release Please to native GitHub Actions. While it correctly removes the old configuration files, it appears to be incomplete as the new GitHub Actions workflow files that should replace this functionality are missing. Merging this pull request in its current state would likely break your repository's commit linting and release process. Please add the new GitHub Actions workflow files to this pull request to complete the migration.

[gemini-code-assist]

Code Review

This pull request aims to migrate from Google GitHub Apps for Conventional Commits and Release Please to native GitHub Actions. While the removal of the old configuration files (.github/conventional-commit-lint.yaml, .github/release-please.yml, .github/release-trigger.yml) is a correct step in this migration, the pull request appears to be incomplete. It is missing the new GitHub Actions workflow files that should replace the functionality of the deprecated apps. Without these new workflows, the repository will lose its automated conventional commit linting and release management capabilities. Please add the corresponding GitHub Actions workflow files to this pull request to complete the migration.