chore: replace old partner teams with new ones (Wave 2)

[suztomo]

Replacing old partner teams with new ones as part of Wave 2 migration. b/478003109

As part of this change, we are also removing admin permissions from the repository settings in .github/sync-repo-settings.yaml. Teams that previously had admin access have been removed or updated to have push access.

[gemini-code-assist]

Summary of Changes

Hello @suztomo, 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 updates the code ownership configuration to reflect current team structures, specifically migrating an old partner team alias to a new one for the BigQuery JDBC driver. This ensures that future changes to the BigQuery JDBC driver are correctly routed to the appropriate development team for review and approval.

Highlights

• Codeowners Update: Replaced the outdated team alias @googleapis/bq-developer-tools with the new team alias @googleapis/bigquery-developer-tools-team for the google-cloud-bigquery-jdbc directory in the .github/CODEOWNERS file.

Changelog

• .github/CODEOWNERS
  • Updated the team responsible for the google-cloud-bigquery-jdbc path.

Activity

• No specific activity has been recorded for this pull request yet.

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]

Code Review

The pull request correctly updates the .github/CODEOWNERS file to replace the legacy team handle @googleapis/bq-developer-tools with the new @googleapis/bigquery-developer-tools-team for the google-cloud-bigquery-jdbc directory. This change is consistent with the stated goal of the Wave 2 migration and ensures that the correct team is notified for changes in this component.