Add CODEOWNERS file

[onderay]

This PR adds a CODEOWNERS file to automatically assign @kinde-oss/giants-kinde as reviewers for all changes.

Summary by CodeRabbit

• Chores
  • Updated repository configuration to assign code ownership.

This release contains only internal configuration updates with no user-facing changes.

[coderabbitai]

Walkthrough

A CODEOWNERS file entry is added to assign ownership of all repository paths to a team. This is a configuration-only change with no impact on code logic or public APIs.

Changes

Cohort / File(s)	Summary
Repository configuration CODEOWNERS	Added CODEOWNERS entry assigning all paths (\*) to team ownership

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A whisker-twitch and code is blessed,
With CODEOWNERS set to rest,
The giants claim their rightful keep,
While repos dream in organized sleep! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "Add CODEOWNERS file" is directly and accurately related to the main change in the changeset. The PR adds a CODEOWNERS file to the repository, which is exactly what the title states. The title is concise, clear, and specific without vague language or unnecessary noise. A teammate scanning the repository history would immediately understand that this PR introduces a CODEOWNERS file for automatic code ownership assignment.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch add-codeowners-1761091980

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2f5edee and 81bec1f.

📒 Files selected for processing (1)

• CODEOWNERS (1 hunks)

🔇 Additional comments (1)

CODEOWNERS (1)

1-1: Syntax and format are correct.

The * pattern matches all files in the repository, and @kinde-oss/giants-kinde is in the correct @org/team-name format for GitHub team references. The file placement at the repository root is valid.

However, verify that:

1. The team @kinde-oss/giants-kinde exists in the kinde-oss organization
2. The team has explicit write access to the repository, even if individual members already have access

If either condition is not met, the CODEOWNERS assignment will not work as intended and code owners won't be automatically requested for review.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}