Skip to content

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

Merged
suztomo merged 2 commits intomainfrom
replace-partner-teams-wave2
Feb 23, 2026
Merged

chore: replace old partner teams with new ones (Wave 2)#1606
suztomo merged 2 commits 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

@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 performs a routine maintenance task by updating the designated code owners for the repository. It aligns the repository's ownership with the new organizational structure as part of a Wave 2 migration, ensuring that the correct team is assigned for code reviews and responsibilities going forward.

Highlights

  • CODEOWNERS Update: Replaced the old @googleapis/api-linter team with the new @googleapis/api-design-team in the .github/CODEOWNERS file to reflect updated team ownership.
Changelog
  • .github/CODEOWNERS
    • Updated the designated code owner from @googleapis/api-linter to @googleapis/api-design-team.
Activity
  • No specific activity has been recorded for this pull request yet, beyond its initial creation.
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

The pull request correctly updates the repository owner to @googleapis/api-design-team as part of the Wave 2 migration. However, the descriptive comment at the top of the file still refers to the old team name and should be updated for consistency.

@suztomo suztomo marked this pull request as ready for review February 23, 2026 15:49
@suztomo suztomo requested review from a team and noahdietz February 23, 2026 15:49
@suztomo suztomo merged commit 6c3779d into main Feb 23, 2026
9 checks passed
@suztomo suztomo deleted the replace-partner-teams-wave2 branch February 23, 2026 18:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants