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

[suztomo]

Bug ID: b/479543683

[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 configuration files to reflect a change in the designated Python team. The primary goal is to transition all automated assignments and ownership declarations from an older team identifier to a new, consolidated cloud SDK Python team. This change streamlines the workflow for code reviews, issue management, and general repository maintenance by ensuring that the correct team is engaged for relevant tasks.

Highlights

• Team Migration: Replaced references to the old Python core client libraries team (@googleapis/python-core-client-libraries) with the new unified cloud SDK Python team (@googleapis/cloud-sdk-python-team) across various configuration files.
• Automated Workflow Updates: Ensured that automated processes for code ownership, issue assignment, and pull request assignment now correctly point to the active Python team.

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

This pull request updates the python team names across several configuration files, replacing @googleapis/python-core-client-libraries and potentially other teams with @googleapis/cloud-sdk-python-team. The changes in .github/blunderbuss.yml and .repo-metadata.json are correct. However, in .github/CODEOWNERS, this replacement has resulted in the new team being listed twice on two separate lines. I've added suggestions to remove these redundant entries for better clarity and maintenance.

[gemini-code-assist]

The team @googleapis/cloud-sdk-python-team is listed twice, which is redundant. Please remove the duplicate entry.

*               @googleapis/cloud-sdk-python-team

[gemini-code-assist]

The team @googleapis/cloud-sdk-python-team is listed twice on this line, which is redundant. Please remove the duplicate entry at the end of the line.

/samples/   @googleapis/cloud-sdk-python-team @googleapis/python-samples-owners