chore: add librarian team to librarian.yaml CODEOWNERS#13281
Merged
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request updates the .github/CODEOWNERS file to assign ownership of /librarian.yaml to the @googleapis/cloud-sdk-java-team and @googleapis/cloud-sdk-librarian-team teams. There are no review comments, and I have no additional feedback to provide.
zhumin8
changed the title
blakeli0
approved these changes
May 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Give Librarian team CODEOWNERS on librarian.yaml. This will both notify the team of changes to this file and expedite review of librarian.yaml only changes that do not produce a diff e.g. config refactor or version update without a regen diff.
During migration while hermetic build is still used, this also allows us to expedite updates to librarian.yaml when generation_config.yaml changes.