fix CODEOWNERS syntax

[jeremyschlatter]

If you want to match two or more code owners with the same pattern,
all the code owners must be on the same line. If the code owners are
not on the same line, the pattern matches only the last mentioned code
owner.

• https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners

[gemini-code-assist]

Summary of Changes

Hello @jeremyschlatter, 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 resolves a syntax issue within the CODEOWNERS file. The modification ensures that all designated code owners for a given file pattern are correctly recognized by GitHub, preventing scenarios where only the last listed owner might be assigned for review.

Highlights

• CODEOWNERS Syntax Correction: Corrected the CODEOWNERS file to ensure multiple code owners for the same pattern are listed on a single line, adhering to GitHub's specified syntax for proper recognition.

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 correctly addresses a syntax issue in the CODEOWNERS file. By placing both code owners on the same line for the wildcard pattern, you've ensured that all specified owners will be correctly notified for changes, as per GitHub's documentation. The change is accurate and effective. I have no further comments.