OWNERS_ALIASES: replace Benjamin2037 with bb7133

[wuhuizuo]

What problem does this PR solve?

Issue Number: close #70419

Problem Summary:

Replace member Benjamin2037 with bb7133 in OWNERS_ALIASES, deduplicating members within each SIG. sig-community-* entries are left untouched (they are synced from pingcap/community).

What changed and how does it work?

• OWNERS_ALIASES: Benjamin2037 -> bb7133 in all SIGs except sig-community-*; removed duplicate bb7133 entries where the same SIG already listed it.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[coderabbitai]

📝 Walkthrough

Walkthrough

OWNERS_ALIASES now uses bb7133 instead of Benjamin2037 in multiple SIG approver aliases.

Changes

Approver membership updates

Layer / File(s)	Summary
Replace approver alias member OWNERS_ALIASES	Replaces Benjamin2037 with bb7133 across the affected SIG approver aliases.

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

Possibly related PRs

• pingcap/tidb#70391: Updates overlapping OWNERS approval configurations.
• pingcap/tidb#70404: Modifies OWNERS_ALIASES approver memberships.
• pingcap/tidb#70405: Applies related OWNERS_ALIASES membership synchronization.

Suggested labels: type/enhancement

Poem

A bunny checked the aliases bright,
Swapped one name with care and light.
bb7133 now joins the queue,
Across SIGs in a tidy crew.
Hop, hop—approvals stay in view!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.
Description check	✅ Passed	The description includes the required issue reference, problem summary, change details, test status, side effects, documentation, and release note sections.
Title check	✅ Passed	The title clearly and concisely describes the primary change: replacing Benjamin2037 with bb7133 in OWNERS_ALIASES.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch update-owner-aliases-bb7133-release-nextgen-202603

---

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

[bb7133]

LGTM. Verified the scoped OWNERS_ALIASES identity replacement and per-SIG deduplication; sig-community aliases are untouched.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bb7133

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [bb7133]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-08-11 03:37:17.256703607 +0000 UTC m=+3104023.292798663: ☑️ agreed by bb7133.

[ti-chi-bot]

@wuhuizuo: You cannot manually add or delete the reviewing state labels, only I and the tursted members have permission to do so.

Details

In response to adding label named lgtm.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.