Skip to content

chore: cleanup release-please config #4013

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
diegomarquezp wants to merge 2 commits into
base: main
Choose a base branch
from
Open

chore: cleanup release-please config #4013

diegomarquezp wants to merge 2 commits into from

Conversation

@diegomarquezp
Copy link
Contributor

@diegomarquezp diegomarquezp commented Dec 5, 2025

This PR cleans up the .github/release-please.yml file by removing redundant options and the bump-minor-pre-major setting for major releases.

@diegomarquezp diegomarquezp requested review from a team as code owners December 5, 2025 16:27
@diegomarquezp diegomarquezp requested a review from suzmue December 5, 2025 16:27
@product-auto-label product-auto-label bot added size: m Pull request size is medium. api: bigquery Issues related to the googleapis/java-bigquery API. labels Dec 5, 2025
@gemini-code-assist
Copy link
Contributor

gemini-code-assist bot commented Dec 5, 2025

Summary of Changes

Hello @diegomarquezp, 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 focuses on cleaning up and simplifying the .github/release-please.yml configuration file. The primary goal is to reduce redundancy by consolidating common release options, such as bumpMinorPreMajor and handleGHRelease, to a global level. This change makes the release process configuration more concise, easier to read, and more maintainable for future updates.

Highlights

  • Configuration Consolidation: The bumpMinorPreMajor and handleGHRelease options have been moved from individual branch configurations to the global release-please configuration, reducing redundancy and simplifying the overall setup.
  • Redundant Option Removal: Duplicate bumpMinorPreMajor and handleGHRelease settings were removed from various branch definitions within the .github/release-please.yml file, making the configuration cleaner.
  • Streamlined Release Types: The releaseType: java-yoshi setting is now defined globally, simplifying the configuration for branches that use this type, while specific releaseType settings for other branches (e.g., java-lts, java-backport) are appropriately retained.
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. ↩

gemini-code-assist[bot]
gemini-code-assist bot reviewed Dec 5, 2025
View reviewed changes
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 does a good job of cleaning up the release-please.yml configuration by removing redundant settings from individual branch configurations. This improves the file's readability and maintainability. I have one suggestion regarding the bumpMinorPreMajor setting to ensure the changes fully align with the intent described in the pull request. Please see my detailed comment.

@diegomarquezp
chore: cleanup release-please config
0dceaff 
- Remove redundant options already declared at the top level.\n- Remove bumpMinorPreMajor for repositories after the first major release.
@diegomarquezp diegomarquezp force-pushed the chore/cleanup-release-please branch from 3c719d3 to 0dceaff Compare December 5, 2025 16:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@suzmue suzmue Awaiting requested review from suzmue suzmue is a code owner automatically assigned from googleapis/api-bigquery

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

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

api: bigquery Issues related to the googleapis/java-bigquery API. size: m Pull request size is medium.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@diegomarquezp