Skip to content

chore: replace old python teams with cloud-sdk-python-team#207

Closed
suztomo wants to merge 1 commit intogoogleapis:mainfrom
suztomo:replace-python-team
Closed

chore: replace old python teams with cloud-sdk-python-team#207
suztomo wants to merge 1 commit intogoogleapis:mainfrom
suztomo:replace-python-team

Conversation

@suztomo
Copy link
Member

@suztomo suztomo commented Feb 2, 2026

Bug ID: b/479543683

@product-auto-label product-auto-label bot added size: s Pull request size is small. api: bigquery Issues related to the googleapis/python-bigquery-magics API. labels Feb 2, 2026
@gemini-code-assist
Copy link

Summary of Changes

Hello @suztomo, 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 centralizes and updates the references to the Python development team across various repository configuration files. By replacing outdated team names with cloud-sdk-python-team, it streamlines the process for assigning code ownership, issues, and pull requests, ensuring that the correct team is notified and responsible for relevant changes.

Highlights

  • Code Ownership Update: The pull request updates the .github/CODEOWNERS file to replace references to @googleapis/yoshi-python and @googleapis/python-core-client-libraries with the new @googleapis/cloud-sdk-python-team for both default and sample-specific code ownership.
  • Automated Assignment Configuration: The blunderbuss.yml file has been modified to use googleapis/cloud-sdk-python-team for assigning issues and pull requests, replacing the older googleapis/python-core-client-libraries team across all relevant sections.
  • Repository Metadata Alignment: The .repo-metadata.json file's codeowner_team field has been updated to reflect the new @googleapis/cloud-sdk-python-team, ensuring consistency across repository configurations.
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.

Copy link

@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 updates the Python team owners from @googleapis/yoshi-python and @googleapis/python-core-client-libraries to @googleapis/cloud-sdk-python-team across various configuration files. The changes are mostly correct, but I've identified a duplicated team entry in the .github/CODEOWNERS file that should be addressed.

Comment on lines 8 to 9
# @googleapis/cloud-sdk-python-team @googleapis/cloud-sdk-python-team @googleapis/api-bigquery-dataframe are the default owners for changes in this repo
* @googleapis/cloud-sdk-python-team @googleapis/cloud-sdk-python-team @googleapis/api-bigquery-dataframe

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The team @googleapis/cloud-sdk-python-team is duplicated in both the comment and the rule. This is likely a result of the autogeneration process replacing two old teams with the same new one. Please remove the duplicate entry. You might need to adjust the configuration for the generation script to prevent this from happening again.

# @googleapis/cloud-sdk-python-team @googleapis/api-bigquery-dataframe are the default owners for changes in this repo
*     @googleapis/cloud-sdk-python-team @googleapis/api-bigquery-dataframe

@suztomo suztomo force-pushed the replace-python-team branch from 72a4904 to 2d37abe Compare February 2, 2026 16:13
@suztomo suztomo closed this Feb 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: bigquery Issues related to the googleapis/python-bigquery-magics API. size: s Pull request size is small.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant