Skip to content

chore: replace old spanner teams in metadata and config#4357

Merged
suztomo merged 2 commits intomainfrom
fix-spanner-team-metadata
Feb 18, 2026
Merged

chore: replace old spanner teams in metadata and config#4357
suztomo merged 2 commits intomainfrom
fix-spanner-team-metadata

Conversation

@suztomo
Copy link
Member

@suztomo suztomo commented Feb 18, 2026

This PR replaces @googleapis/spanner-client-libraries-java with @googleapis/spanner-team in .repo-metadata.json and generation_config.yaml. b/478003109

@suztomo suztomo requested review from a team as code owners February 18, 2026 18:02
@product-auto-label product-auto-label bot added size: xs Pull request size is extra small. api: spanner Issues related to the googleapis/java-spanner API. labels Feb 18, 2026
@gemini-code-assist
Copy link
Contributor

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 the references to the Spanner team in the repository's configuration and metadata files. The change ensures that the correct team is designated as the code owner for the Spanner client libraries, aligning with internal team restructuring and maintaining accurate project metadata.

Highlights

  • Codeowner Team Update: The Spanner codeowner team reference has been updated from @googleapis/spanner-client-libraries-java to @googleapis/spanner-team across various configuration files.
  • Configuration File Changes: The .github/CODEOWNERS, .repo-metadata.json, and generation_config.yaml files were modified to reflect the new team name.
Changelog
  • .github/CODEOWNERS
    • Updated the default code owner for the repository to the new Spanner team.
  • .repo-metadata.json
    • Modified the codeowner_team field to reflect the updated Spanner team name.
  • generation_config.yaml
    • Updated the codeowner_team entry for the Spanner library to the new team name.
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.

Copy link
Contributor

@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

This pull request updates the Spanner team name from @googleapis/spanner-client-libraries-java to @googleapis/spanner-team across configuration files. The changes in .github/CODEOWNERS, .repo-metadata.json, and generation_config.yaml are consistent and correctly reflect the intended update. The changes look good.

@suztomo suztomo merged commit b92b5b3 into main Feb 18, 2026
31 of 33 checks passed
@suztomo suztomo deleted the fix-spanner-team-metadata branch February 18, 2026 18:53
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/java-spanner API. size: xs Pull request size is extra small.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments