chore: remove api-bigtable-partners

[suztomo]

Removing api-bigtable-partners from configuration files.

b/481375128

[gemini-code-assist]

Summary of Changes

Hello @suztomo, 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 streamlines repository configuration by systematically removing all references to the api-bigtable-partners team. This change affects how code ownership, issue assignment, and pull request reviews are managed, ensuring that only active and relevant teams are included in the automation workflows and metadata.

Highlights

• CODEOWNERS Update: The @googleapis/api-bigtable-partners team has been removed from the default and samples-specific code ownership rules in .github/CODEOWNERS.
• Blunderbuss Configuration Streamlining: References to @googleapis/api-bigtable-partners have been removed from issue and pull request assignment configurations in .github/blunderbuss.yml.
• Repository Metadata Adjustment: The codeowner_team entry in both .librarian/generator-input/.repo-metadata.json and .repo-metadata.json has been updated to exclude @googleapis/api-bigtable-partners.

Changelog

• .github/CODEOWNERS
  • Removed @googleapis/api-bigtable-partners from the main ownership line.
  • Removed @googleapis/api-bigtable-partners from the /samples/ directory ownership line.
• .github/blunderbuss.yml
  • Removed @googleapis/api-bigtable-partners from the assign_issues list.
  • Removed @googleapis/api-bigtable-partners from the assign_issues_by for "samples" label.
  • Removed @googleapis/api-bigtable-partners from the assign_prs list.
• .librarian/generator-input/.repo-metadata.json
  • Updated the codeowner_team field to remove @googleapis/api-bigtable-partners.
• .repo-metadata.json
  • Updated the codeowner_team field to remove @googleapis/api-bigtable-partners.

Activity

• No human activity (comments, reviews, etc.) 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. ↩

[gemini-code-assist]

Code Review

This pull request removes the api-bigtable-partners team from various configuration files. The changes are consistent across .github/CODEOWNERS, .github/blunderbuss.yml, and the repo-metadata.json files. The modifications correctly update the repository's ownership and issue assignment settings. The changes are straightforward and look good.

[suztomo]

Let's wait for Monorepo Migration.