Skip to content

chore: Removing dee-infra from CODEOWNERS and Blunderbuss config files#4084

Merged
iennae merged 1 commit intomainfrom
chore-dee-infra-cleanup
May 7, 2025
Merged

chore: Removing dee-infra from CODEOWNERS and Blunderbuss config files#4084
iennae merged 1 commit intomainfrom
chore-dee-infra-cleanup

Conversation

@rsamborski
Copy link
Copy Markdown
Member

Description

Removing dee-infra from CODEOWNERS and Blunderbuss config files

Checklist

@rsamborski rsamborski requested review from a team as code owners May 7, 2025 21:47
@product-auto-label product-auto-label Bot added the samples Issues that are directly related to samples. label May 7, 2025
Copy link
Copy Markdown
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.

Hello @rsamborski, 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!

Summary of Changes

This pull request removes the dee-infra team from the CODEOWNERS file. This change means that the dee-infra team will no longer be automatically assigned as reviewers for changes to the listed files and directories. The PR also removes dee-infra from the Blunderbuss config files.

Highlights

  • CODEOWNERS Update: The primary change is the removal of @GoogleCloudPlatform/dee-infra from several lines in the CODEOWNERS file, specifically those related to infrastructure components like auth, batch, compute, iam, kms, orgpolicy, recaptcha_enterprise, secret-manager, parametermanager, service-directory, tpu, and webrisk.
  • Blunderbuss Configuration: The dee-infra team is removed from the Blunderbuss configuration, which affects how reviewers are automatically assigned to pull requests.

Changelog

  • CODEOWNERS
    • Removed @GoogleCloudPlatform/dee-infra from the following lines: 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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.


A team departs,
Code ownership shifts anew,
The system evolves.

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
Copy Markdown
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 removes the dee-infra team from the CODEOWNERS file. The change seems straightforward and necessary. I have reviewed the changes and provided feedback.

Merge Readiness

The pull request is ready to be merged as it simply removes a team from the CODEOWNERS file. I am unable to directly approve the pull request, and users should have others review and approve this code before merging.

@iennae iennae merged commit 72824d9 into main May 7, 2025
15 checks passed
@iennae iennae deleted the chore-dee-infra-cleanup branch May 7, 2025 22:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

samples Issues that are directly related to samples.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants