chore: update ownership/routing for repo

[shollyman]

This PR effectively moves ownership for this repo to the python language team, and removes api-bigquery as the defacto code owner.

[gemini-code-assist]

Summary of Changes

Hello @shollyman, 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 implements a significant shift in the repository's administrative structure by reassigning its core ownership. The changes move the responsibility for code maintenance, review, and issue management to the Python language team, specifically the python-core-client-libraries group. This ensures that the repository's routing and assignment mechanisms are updated to reflect this new organizational alignment, streamlining future development and support processes under the designated Python team.

Highlights

• Code Ownership Transfer: The primary code ownership for the repository has been transferred from the api-bigquery team to the python-core-client-libraries team.
• Automated Assignment Updates: The Blunderbuss configuration has been updated to reflect the new ownership, ensuring issues and pull requests are automatically assigned to the python-core-client-libraries team.
• Repository Metadata Alignment: The .repo-metadata.json file has been modified to align the codeowner_team entry with the new Python language team's ownership.

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 repository ownership from api-bigquery to the python-core-client-libraries team. The changes are consistent across .repo-metadata.json, .github/CODEOWNERS, and .github/blunderbuss.yml. My review feedback focuses on a maintainability best practice: since .github/CODEOWNERS and .github/blunderbuss.yml are autogenerated, they should not be manually edited or included in this pull request. Only the source file, .repo-metadata.json, should be changed, allowing automation to handle the regeneration of the other files. This approach helps keep the repository history clean and avoids potential merge conflicts.

[chalmerlowe]

LGTM