Skip to content

Comments

chore: replace old partner teams with new ones (Wave 2)#1759

Draft
suztomo wants to merge 1 commit intomainfrom
replace-partner-teams-wave2
Draft

chore: replace old partner teams with new ones (Wave 2)#1759
suztomo wants to merge 1 commit intomainfrom
replace-partner-teams-wave2

Conversation

@suztomo
Copy link
Member

@suztomo suztomo commented Feb 20, 2026

Replacing old partner teams with new ones as part of Wave 2 migration. b/478003109

@product-auto-label product-auto-label bot added size: xs Pull request size is extra small. api: storage Issues related to the googleapis/python-storage API. labels Feb 20, 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 systematically updates the repository's team ownership configurations to align with a new organizational structure. The changes ensure that the correct teams are assigned responsibility for code areas and metadata, facilitating proper review workflows and team accountability following a migration wave.

Highlights

  • Codeowner Team Migration: The pull request updates the designated codeowner teams across multiple configuration files, replacing older team aliases with new ones as part of a Wave 2 migration.
  • Configuration File Updates: Changes were applied to .github/CODEOWNERS, .librarian/generator-input/.repo-metadata.json, and .repo-metadata.json to reflect the new team structure.
Changelog
  • .github/CODEOWNERS
    • Updated the default codeowner teams from @googleapis/yoshi-python @googleapis/gcs-fs to @googleapis/cloud-sdk-platform-team-python @googleapis/gcs-internal-client-team.
  • .librarian/generator-input/.repo-metadata.json
    • Modified the codeowner_team field to reflect the new team aliases.
  • .repo-metadata.json
    • Modified the codeowner_team field to reflect the new team aliases.
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 code ownership information across several configuration files, replacing old team aliases with new ones. The changes are mostly consistent, but I've noted one minor issue in the .github/CODEOWNERS file where a comment could be updated to fully reflect the changes in ownership. Otherwise, the updates in .repo-metadata.json and .librarian/generator-input/.repo-metadata.json are correct.


# @googleapis/yoshi-python @googleapis/gcs-sdk-team are the default owners for changes in this repo
* @googleapis/yoshi-python @googleapis/gcs-sdk-team @googleapis/gcs-fs
# @googleapis/cloud-sdk-platform-team-python @googleapis/gcs-sdk-team are the default owners for changes in this repo
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The comment describing the default owners is now out of sync with the rule on the next line. To improve clarity and maintainability, please update the comment to include @googleapis/gcs-internal-client-team to accurately reflect the full list of default owners.

# @googleapis/cloud-sdk-platform-team-python @googleapis/gcs-sdk-team @googleapis/gcs-internal-client-team are the default owners for changes in this repo

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

Labels

api: storage Issues related to the googleapis/python-storage API. size: xs Pull request size is extra small.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant