Skip to content

chore: replace old spanner and python teams with new teams#1498

Open
suztomo wants to merge 1 commit intomainfrom
replace-old-team
Open

chore: replace old spanner and python teams with new teams#1498
suztomo wants to merge 1 commit intomainfrom
replace-old-team

Conversation

@suztomo
Copy link
Member

@suztomo suztomo commented Feb 19, 2026

b/478003109

@product-auto-label product-auto-label bot added size: s Pull request size is small. api: spanner Issues related to the googleapis/python-spanner API. labels Feb 19, 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 updates team references across several configuration files to reflect recent organizational changes. The primary goal is to ensure that code ownership, issue assignment, and pull request review processes are correctly routed to the new Python and Spanner teams, maintaining accurate automation and responsibility mapping within the repository.

Highlights

  • Team Name Updates: Replaced the old @googleapis/yoshi-python team with @googleapis/cloud-sdk-python-team in the CODEOWNERS file.
  • Spanner Team Renaming: Updated all occurrences of @googleapis/spanner-client-libraries-python to @googleapis/spanner-team across various configuration files.
  • Automated Assignment Configuration: Modified blunderbuss.yml to reflect the new Spanner team name for issue and pull request assignments.
  • Metadata Synchronization: Synchronized the codeowner_team field in both .librarian/generator-input/.repo-metadata.json and .repo-metadata.json to use the new Spanner team name.
Changelog
  • .github/CODEOWNERS
    • Updated the default owners for the entire repository from @googleapis/yoshi-python and @googleapis/spanner-client-libraries-python to @googleapis/cloud-sdk-python-team and @googleapis/spanner-team.
    • Changed the owners for the /samples/ directory from @googleapis/python-samples-reviewers and @googleapis/spanner-client-libraries-python to @googleapis/python-samples-reviewers and @googleapis/spanner-team.
  • .github/blunderbuss.yml
    • Updated the team assigned for general issues from googleapis/spanner-client-libraries-python to googleapis/spanner-team.
    • Modified the team assigned for issues with the 'samples' label from googleapis/spanner-client-libraries-python to googleapis/spanner-team.
    • Changed the team assigned for pull requests from googleapis/spanner-client-libraries-python to googleapis/spanner-team.
  • .librarian/generator-input/.repo-metadata.json
    • Updated the codeowner_team value from @googleapis/spanner-client-libraries-python to @googleapis/spanner-team.
  • .repo-metadata.json
    • Updated the codeowner_team value from @googleapis/spanner-client-libraries-python to @googleapis/spanner-team.
Activity
  • No human activity has been recorded on this pull request yet.
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.

@suztomo suztomo marked this pull request as ready for review February 19, 2026 01:49
@suztomo suztomo requested review from a team as code owners February 19, 2026 01:49
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

The pull request successfully updates the team names in .github/CODEOWNERS, .github/blunderbuss.yml, and .librarian/generator-input/.repo-metadata.json to reflect the new Python and Spanner teams. The changes are straightforward and align with the PR title and description.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments