chore: add code owner

[bzp2010]

Summary by CodeRabbit

• Chores
  • Updated internal code ownership configuration for review workflows.

[coderabbitai]

📝 Walkthrough

Walkthrough

A .github/CODEOWNERS file was added to specify code ownership. The file designates a single user as the code owner for all repository paths, establishing the ownership metadata used by GitHub's code review and approval workflows.

Changes

Cohort / File(s)	Summary
Configuration .github/CODEOWNERS	New file added defining code ownership assignment for repository-wide paths.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore: add code owner' accurately describes the main change: adding a .github/CODEOWNERS file with code owner assignments.
E2e Test Quality Review	✅ Passed	PR adds only .github/CODEOWNERS configuration file with no code implementation, tests, or functional changes; E2E test review criteria do not apply to metadata configuration changes.
Security Check	✅ Passed	The CODEOWNERS file contains only administrative metadata with no sensitive data, credentials, secrets, or security-related code.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bzp/chore-codeowner-bzp2010

---

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

[coderabbitai]

🧹 Nitpick comments (1)

.github/CODEOWNERS (1)

1-1: LGTM! Valid CODEOWNERS configuration.

The syntax is correct and will assign @bzp2010 as the code owner for all files in the repository. This is a straightforward initial setup.

---

Optional: Consider adding a comment for documentation.

While not required, adding a brief comment above the ownership rule can help document the ownership structure for future maintainers.

📝 Optional enhancement to add documentation

+# Default code owner for all files
 * `@bzp2010`

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.github/CODEOWNERS at line 1, Add a brief documentation comment above the
CODEOWNERS entry to explain the ownership rule; update the line containing "*
`@bzp2010`" by inserting a short comment (e.g., "Repository-wide owner: `@bzp2010`")
immediately above it so future maintainers understand that the wildcard assigns
`@bzp2010` as code owner for all files.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In @.github/CODEOWNERS:
- Line 1: Add a brief documentation comment above the CODEOWNERS entry to
explain the ownership rule; update the line containing "* `@bzp2010`" by inserting
a short comment (e.g., "Repository-wide owner: `@bzp2010`") immediately above it
so future maintainers understand that the wildcard assigns `@bzp2010` as code
owner for all files.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a5d47850-e4f2-4471-91de-54c067779a5f

📥 Commits

Reviewing files that changed from the base of the PR and between 0e33626 and 25442d5.

📒 Files selected for processing (1)

• .github/CODEOWNERS