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 centralizes the ownership and assignment of Python-related tasks by migrating from several older, disparate Python teams to a single, unified cloud-sdk-python-team. This change streamlines the process for code reviews, issue assignments, and general code ownership, ensuring consistency and clarity in team responsibilities across the repository's configuration files.

Highlights

• CODEOWNERS Update: The default code owner for the repository has been updated from @googleapis/python-core-client-libraries to the new @googleapis/cloud-sdk-python-team.
• Blunderbuss Configuration Change: The blunderbuss.yml file has been modified to assign issues and pull requests, including those with the 'samples' label, to the new cloud-sdk-python-team instead of googleapis/actools-python.
• Repository Metadata Alignment: The codeowner_team field in .repo-metadata.json has been updated to reflect the new @googleapis/cloud-sdk-python-team, ensuring consistency across repository configuration.

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 team names in configuration files. The changes in .github/CODEOWNERS and .repo-metadata.json are correct. However, .github/blunderbuss.yml is an autogenerated file and has been edited manually. To adhere to repository best practices and prevent future inconsistencies, this file should be updated by running its corresponding generator script rather than by direct editing.

[gemini-code-assist]

This file is marked as autogenerated. Per repository guidelines, generated files should not be edited manually. Instead, please run the generator that creates this file after updating its source (.repo-metadata.json). This ensures that all changes are applied consistently and prevents manual edits from being accidentally overwritten.

References

1. For generated code, apply fixes to the generator templates rather than patching individual output files to ensure consistency across the codebase.