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 focuses on a maintenance task to update the code ownership configuration for the repository. It ensures that the correct and current Python team is designated as the default owner for code changes, streamlining the review process and aligning with current team structures. This change improves the maintainability of the repository by ensuring that the appropriate team is automatically notified for relevant pull requests.

Highlights

• CODEOWNERS Update: The .github/CODEOWNERS file has been updated to reflect changes in team ownership.
• Python Team Replacement: The @googleapis/yoshi-python team has been replaced with the new @googleapis/cloud-sdk-python-team as the default code owner for the repository.

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 in the CODEOWNERS file. My review points out a potential issue with how the change was made. A comment in the CODEOWNERS file indicates that it is autogenerated, and that any changes should be made in .repo-metadata.json instead. Modifying the CODEOWNERS file directly could result in your changes being overwritten.

[gemini-code-assist]

The comment on line 6 indicates that this file is autogenerated and that changes should be made in .repo-metadata.json. By changing this file directly, your changes risk being overwritten by an automated process. To ensure this update is permanent, please apply the change to .repo-metadata.json instead.