OWNERS: Auto Sync OWNERS files from community membership

[ti-chi-bot]

Check List

Tests

• No need to test

  • I checked and no code files have been changed.

Summary by CodeRabbit

• Chores
  • Added repository-wide ownership and review assignments.
  • Defined reviewer and approver groups for managing code changes.
  • Documented that group membership is synchronized from the community repository.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: c647d5c5-947a-4ac4-aa50-fd78ff6cdb9b

📥 Commits

Reviewing files that changed from the base of the PR and between 1578bc3 and e4441ba.

📒 Files selected for processing (2)

• OWNERS
• OWNERS_ALIASES

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The change adds community reviewer and approver aliases and assigns them to all repository paths through the new OWNERS configuration.

Changes

Community ownership

Layer / File(s)	Summary
Community owner aliases OWNERS_ALIASES	Defines sig-community-reviewers and sig-community-approvers with their GitHub usernames.
Repository ownership rules OWNERS	Assigns the community aliases to all paths through the .* filter. Approvers receive approval rights, and reviewers receive review rights.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to e4441

This change adds repository ownership and community membership mappings without introducing an actionable merge-blocking risk; it is merge-ready after normal checks and review.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description only includes the test checklist. It omits the required What is changed?, Any related PRs or issues?, and Which version does your change affect? sections and does not explain the OWNER…	Add all required template sections. Describe the OWNERS and OWNERS_ALIASES changes, provide related PR or issue references or state that none exist, and specify the affected version.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: automatic synchronization of OWNERS files from community membership.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Description check

Explanation

The description only includes the test checklist. It omits the required What is changed?, Any related PRs or issues?, and Which version does your change affect? sections and does not explain the OWNERS updates.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bot/update-owners-1788133989805

---

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.}

[ti-chi-bot]

/release-note-none