Skip to content

Conversation

@holtskinner
Copy link
Member

  • release-please GitHub App is being turned down on August 15, 2025

- release-please GitHub App is being turned down on August 15, 2025
@holtskinner holtskinner requested a review from a team as a code owner August 1, 2025 16:59
Copy link
Contributor

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

Summary of Changes

Hello @holtskinner, 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 begins the process of updating the project's automated release mechanism. It removes the existing configuration for the release-please GitHub App, which is scheduled for deprecation, thereby preparing the repository for a new, GitHub Action-driven release workflow to maintain continuous integration and delivery practices.

Highlights

  • Release Automation Migration: Initiating the migration of the project's release automation from the release-please GitHub App to a GitHub Action-based approach, in anticipation of the App's deprecation.
  • Configuration Removal: Removing the legacy configuration files (.github/release-please.yml and .github/release-trigger.yml) that were used by the release-please GitHub App.
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.

Copy link
Contributor

@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 aims to migrate from the release-please GitHub App to the corresponding GitHub Action, which is a necessary change as the app is being deprecated. The changes correctly remove the configuration files for the old app. However, the new GitHub Action workflow that should replace it is missing from this PR. This omission is critical as it will break the release process. Please add the new workflow file to complete the migration.

@holtskinner holtskinner merged commit 760697f into main Aug 1, 2025
8 checks passed
@holtskinner holtskinner deleted the update-release-please branch August 1, 2025 17:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants