chore: add @opentdf/documentation as codeowners for all content

[jp-ayyappan]

Summary

• Adds @opentdf/documentation team to the catch-all * rule so that all changes to this repo require documentation team approval
• @opentdf/maintainers approval is still required alongside the documentation team

Changes

-* @opentdf/maintainers
+* @opentdf/maintainers @opentdf/documentation

Since this entire repo is documentation, all content changes should require sign-off from the documentation team.

🤖 Generated with Claude Code

[gemini-code-assist]

Summary of Changes

Hello, 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 formalizes the review process for this documentation-focused repository by integrating the @opentdf/documentation team into the CODEOWNERS file. This change ensures that all content modifications receive explicit approval from the documentation team, in addition to the existing maintainer approval, thereby enhancing the quality and consistency of the documentation.

Highlights

• CODEOWNERS Update: Added the @opentdf/documentation team to the catch-all * rule in CODEOWNERS, requiring their approval for all changes across the repository.
• Approval Requirements: Ensured that @opentdf/maintainers approval is still required alongside the newly added documentation team approval for all repository modifications.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• CODEOWNERS
  • Updated the catch-all rule to include the @opentdf/documentation team.

Activity

• No specific activity has been recorded for this pull request since its 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. ↩

[gemini-code-assist]

Code Review

This pull request updates the CODEOWNERS file to add the @opentdf/documentation team to the default rule, requiring their review on most changes. To improve the file's clarity and maintainability, I've suggested adding a comment to explain the rationale behind this rule, consistent with existing patterns in the file.

[gemini-code-assist]

For improved clarity and maintainability, it's good practice to add a comment explaining the purpose of this catch-all rule. This follows the precedent set on line 3 for other specific rules and helps others understand why the documentation team is a required reviewer.

# All content changes require review from the documentation team
* @opentdf/maintainers @opentdf/documentation

[jp-ayyappan]

Addressed — added a comment above the catch-all rule explaining the documentation team requirement, as suggested.