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 configuration.
  • Added reviewer and approver team aliases for community contributions.
  • Documented links and membership synchronization guidance.

[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: fbdb5a37-5315-46ec-840b-3dc5ebe78204

📥 Commits

Reviewing files that changed from the base of the PR and between c12047a and 84361c1.

📒 Files selected for processing (2)

• OWNERS
• OWNERS_ALIASES

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

---

📝 Walkthrough

Walkthrough

The PR adds repository-wide ownership rules and defines SIG Community reviewer and approver aliases with synchronized membership lists.

Changes

Repository ownership

Layer / File(s)	Summary
SIG Community team aliases OWNERS_ALIASES	Defines reviewer and approver aliases with GitHub membership lists synchronized from the TiKV community repository.
Repository ownership rules OWNERS	Assigns the SIG Community approver and reviewer aliases to all repository paths.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Merge Risk: ⚪ Minimal · up to 84361

This change adds repository ownership rules and community reviewer/approver aliases; no actionable merge-blocking risk remains beyond 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 a test checklist. It omits the required problem statement, issue number, change details, code-change classification, side effects, and related changes sections.	Complete the repository template. State the problem and issue number, describe the OWNERS synchronization change, select "No code" under Code changes, select "No need to test" with its reason, select "NO side effects," and select "NO relate…

✅ 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. It is concise and specific.
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

Resolution

Complete the repository template. State the problem and issue number, describe the OWNERS synchronization change, select "No code" under Code changes, select "No need to test" with its reason, select "NO side effects," and select "NO related changes" or provide applicable details.

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 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

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

---

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