Skip to content

OWNERS: sync master to release-7.5 - #68871

Closed
ti-chi-bot wants to merge 0 commit into
release-7.5from
bot/sync-owners-to-release-7.5
Closed

ti-chi-bot wants to merge 0 commit into
release-7.5from
bot/sync-owners-to-release-7.5

Conversation

@ti-chi-bot

@ti-chi-bot ti-chi-bot commented Jun 2, 2026

Copy link
Copy Markdown
Member

What problem does this PR solve?

Sync OWNERS* files from master to release-7.5.

What changed and how does it work?

This PR was auto-generated by Prow and only updates OWNERS and OWNERS_ALIASES files.

/release-note-none
skip-issue-check
lgtm
approved
cherry-pick-approved

Summary by CodeRabbit

  • Chores
    • Restructured root code review ownership configuration to use pattern-based approvers instead of explicit lists
    • Expanded approver group definitions with new community and statistics review teams
    • Added explicit code review ownership configurations across multiple package directories for clearer approval routing

@ti-chi-bot ti-chi-bot added approved cherry-pick-approved Cherry pick PR approved by release team. lgtm skip-issue-check Indicates that a PR no need to check linked issue. labels Jun 2, 2026
@ti-chi-bot

ti-chi-bot Bot commented Jun 2, 2026

Copy link
Copy Markdown

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Details

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 kubernetes-sigs/prow repository.

@ti-chi-bot ti-chi-bot Bot added do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. sig/planner SIG: Planner size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed approved labels Jun 2, 2026
@coderabbitai

coderabbitai Bot commented Jun 2, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

The PR restructures TiDB's code ownership model from hardcoded GitHub username lists to a filter-based group system. Root OWNERS transitions to patterns for dependency and community approvals; OWNERS_ALIASES expands with new approver/reviewer team groups. Package-level OWNERS files are introduced across 24 directories to apply specific approver assignments within executor, backup, lighting, core, and server configuration subsystems.

OWNERS Restructure

Layer / File(s) Summary
Root OWNERS and OWNERS_ALIASES refactor
OWNERS, OWNERS_ALIASES
Root OWNERS file transitions to filter-based configuration routing go.mod changes to sig-critical-approvers-dep and all other files to sig-community-approvers/sig-community-reviewers; OWNERS_ALIASES expanded with new sig-approvers-stats, sig-approvers-metrics, sig-community-reviewers, and sig-community-approvers groups, and existing approver/reviewer alias memberships updated across multiple SIGs.
Executor subsystem ownership assignments
pkg/executor/OWNERS, pkg/executor/aggfuncs/OWNERS, pkg/executor/aggregate/OWNERS, pkg/executor/join/OWNERS, pkg/executor/mppcoordmanager/OWNERS, pkg/executor/sortexec/OWNERS, pkg/executor/test/analyzetest/OWNERS, pkg/executor/unionexec/OWNERS
Executor and executor submodules assigned to sig-approvers-executor; pkg/executor/test/analyzetest assigned to sig-approvers-stats; base executor OWNERS includes filter for analyze.*.go files routed to stats approvers.
Backup and Lightning subsystem ownership
br/OWNERS, lightning/OWNERS, pkg/lightning/config/OWNERS
br/OWNERS consolidated to top-level sig-approvers-br approver; lightning/OWNERS uses filter pattern assigning tidb-lightning.toml to sig-critical-approvers-tidb-lightning and all other files to sig-approvers-lightning; pkg/lightning/config/OWNERS assigns critical lightning approvers.
Core subsystem ownership (DDL, ingestor, metrics, storage)
pkg/ingestor/OWNERS, pkg/metrics/OWNERS, pkg/objstore/OWNERS, pkg/statistics/OWNERS, pkg/util/naming/OWNERS
pkg/ingestor/OWNERS assigned to sig-approvers-ddl; pkg/metrics/OWNERS assigned to sig-approvers-metrics; pkg/objstore/OWNERS assigned to both sig-approvers-br and sig-approvers-lightning; pkg/statistics/OWNERS updated to add sig-approvers-stats and component/statistics label; pkg/util/naming/OWNERS assigned to sig-approvers-ddl.
Server configuration ownership (meta, session, sessionctx)
pkg/meta/metadef/OWNERS, pkg/session/OWNERS, pkg/sessionctx/vardef/OWNERS
pkg/meta/metadef/OWNERS uses filter patterns assigning OWNERS and system_tables_def.go to sig-critical-approvers-tidb-server, and all other files to sig-approvers-meta; pkg/session/OWNERS updated to split approvals between sig-critical-approvers-tidb-server and sig-approvers-ddl; pkg/sessionctx/vardef/OWNERS uses filter pattern for critical server approvers on sysvar and tidb_vars files.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

  • pingcap/tidb#68706: Both PRs modify the repository's OWNERS/OWNERS_ALIASES ownership definitions by updating approver/reviewer membership and community-related configuration.
  • pingcap/tidb#67717: Both PRs modify the OWNERS approval policy; #67717 directly updates top-level approver/reviewer username lists while this PR reworks OWNERS to use structured filters and group-based entries instead.
  • pingcap/tidb#68869: Both PRs modify OWNERS_ALIASES membership, updating sig-approvers-executor/sig-approvers-expression alias lists and executor-related approver aliases.

Suggested labels

size/L, release-note-none, approved

Suggested reviewers

  • windtalker
  • wshwsh12
  • XuHuaiyu

Poem

🐰 The OWNERS dance in patterns now,
Groups guide each code review's bow,
From hardcoded names to team control,
Filters route each change with soul!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive The description is incomplete relative to the template. It lacks the required 'Issue Number' section and 'Check List' with test selections. Add 'Issue Number: close #xxx' section and complete the 'Check List' section with appropriate test and side effect selections, even if selecting 'No need to test'.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main objective of the PR: syncing OWNERS files from master to release-7.5 branch.
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.

✏️ 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 bot/sync-owners-to-release-7.5

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

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@OWNERS_ALIASES`:
- Line 319: Replace the lowercase entry `yangkeao` with the canonical casing
`YangKeao` in the OWNERS_ALIASES group so it matches other alias groups (e.g.,
sig-approvers-domain, sig-approvers-ddl, sig-approvers-infoschema,
sig-approvers-meta, sig-approvers-owner, sig-approvers-table); update the
single-line alias entry to `YangKeao` to ensure consistent username matching
across all alias lists.
- Line 218: Username casing inconsistency: standardize the alias entry so the
username matches other groups. Replace the uppercase alias "GMHDBJD" with the
lowercase form "gmhdbjd" in the OWNERS_ALIASES entry to ensure consistency with
other groups (e.g., sig-approvers-lightning, sig-approvers-disttask,
sig-approvers-dumpling); update any other occurrences in the same file to the
lowercase form if present, then run the repo's OWNERs validation/lint to confirm
approvals will match.

In `@pkg/executor/OWNERS`:
- Around line 2-7: The OWNERS file sets no_parent_owners: true and only defines
a filter for "analyze.*\\.go$" so other files in pkg/executor/ have no approver;
add a default approver entry (either a top-level approvers: list or a catch-all
filters entry such as ".*" with approvers) so non-analyze files have an explicit
approver group; update the same OWNERS file ensuring you keep no_parent_owners:
true and the existing "analyze.*\\.go$" filter while adding the new default
approvers list (refer to the no_parent_owners, filters, and the
"analyze.*\\.go$" pattern to locate where to add it).
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: ab534ca7-0896-4a1c-99d5-7b897b5f07f8

📥 Commits

Reviewing files that changed from the base of the PR and between 416a6fb and 1ebf6c1.

📒 Files selected for processing (25)
  • OWNERS
  • OWNERS_ALIASES
  • br/OWNERS
  • lightning/OWNERS
  • lightning/cmd/tidb-lightning-ctl/OWNERS
  • lightning/cmd/tidb-lightning/OWNERS
  • pkg/dxf/OWNERS
  • pkg/executor/OWNERS
  • pkg/executor/aggfuncs/OWNERS
  • pkg/executor/aggregate/OWNERS
  • pkg/executor/join/OWNERS
  • pkg/executor/mppcoordmanager/OWNERS
  • pkg/executor/sortexec/OWNERS
  • pkg/executor/test/analyzetest/OWNERS
  • pkg/executor/unionexec/OWNERS
  • pkg/ingestor/OWNERS
  • pkg/lightning/OWNERS
  • pkg/lightning/config/OWNERS
  • pkg/meta/metadef/OWNERS
  • pkg/metrics/OWNERS
  • pkg/objstore/OWNERS
  • pkg/session/OWNERS
  • pkg/sessionctx/vardef/OWNERS
  • pkg/statistics/OWNERS
  • pkg/util/naming/OWNERS

Comment thread OWNERS_ALIASES Outdated
- Deardrops
- Defined2014
- Ehco1996
- GMHDBJD

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Username casing inconsistency: GMHDBJD vs gmhdbjd.

This user appears as GMHDBJD here but as gmhdbjd in other alias groups (e.g., sig-approvers-lightning, sig-approvers-disttask, sig-approvers-dumpling). If the OWNERS system is case-sensitive, this could prevent approval matching.

Proposed fix
-    - GMHDBJD
+    - gmhdbjd
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- GMHDBJD
- gmhdbjd
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@OWNERS_ALIASES` at line 218, Username casing inconsistency: standardize the
alias entry so the username matches other groups. Replace the uppercase alias
"GMHDBJD" with the lowercase form "gmhdbjd" in the OWNERS_ALIASES entry to
ensure consistency with other groups (e.g., sig-approvers-lightning,
sig-approvers-disttask, sig-approvers-dumpling); update any other occurrences in
the same file to the lowercase form if present, then run the repo's OWNERs
validation/lint to confirm approvals will match.

Comment thread OWNERS_ALIASES Outdated
- xhebox
- xiongjiwei
- xuyifangreeneyes
- yangkeao

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Username casing inconsistency: yangkeao vs YangKeao.

This user appears as yangkeao here but as YangKeao in other alias groups (e.g., sig-approvers-domain, sig-approvers-ddl, sig-approvers-infoschema, sig-approvers-meta, sig-approvers-owner, sig-approvers-table). Recommend using consistent casing to avoid potential matching issues.

Proposed fix
-    - yangkeao
+    - YangKeao
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- yangkeao
- YangKeao
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@OWNERS_ALIASES` at line 319, Replace the lowercase entry `yangkeao` with the
canonical casing `YangKeao` in the OWNERS_ALIASES group so it matches other
alias groups (e.g., sig-approvers-domain, sig-approvers-ddl,
sig-approvers-infoschema, sig-approvers-meta, sig-approvers-owner,
sig-approvers-table); update the single-line alias entry to `YangKeao` to ensure
consistent username matching across all alias lists.

Comment thread pkg/executor/OWNERS Outdated
Comment on lines +2 to +7
options:
no_parent_owners: true
filters:
"analyze.*\\.go$":
approvers:
- sig-approvers-stats

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Add a default approver group for non-analyze files.

With no_parent_owners: true, this file currently routes only analyze.*.go and leaves other files in pkg/executor/ without an explicit approver path.

Suggested patch
 options:
   no_parent_owners: true
+approvers:
+  - sig-approvers-executor
 filters:
   "analyze.*\\.go$":
     approvers:
       - sig-approvers-stats
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
options:
no_parent_owners: true
filters:
"analyze.*\\.go$":
approvers:
- sig-approvers-stats
options:
no_parent_owners: true
approvers:
- sig-approvers-executor
filters:
"analyze.*\\.go$":
approvers:
- sig-approvers-stats
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@pkg/executor/OWNERS` around lines 2 - 7, The OWNERS file sets
no_parent_owners: true and only defines a filter for "analyze.*\\.go$" so other
files in pkg/executor/ have no approver; add a default approver entry (either a
top-level approvers: list or a catch-all filters entry such as ".*" with
approvers) so non-analyze files have an explicit approver group; update the same
OWNERS file ensuring you keep no_parent_owners: true and the existing
"analyze.*\\.go$" filter while adding the new default approvers list (refer to
the no_parent_owners, filters, and the "analyze.*\\.go$" pattern to locate where
to add it).

@ti-chi-bot ti-chi-bot closed this Jun 3, 2026
@ti-chi-bot
ti-chi-bot force-pushed the bot/sync-owners-to-release-7.5 branch from 1ebf6c1 to 416a6fb Compare June 3, 2026 06:34
@ti-chi-bot

ti-chi-bot Bot commented Jun 3, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

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

Details Needs approval from an approver in each of these files:

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 ti-chi-bot Bot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Jun 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cherry-pick-approved Cherry pick PR approved by release team. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. lgtm sig/planner SIG: Planner size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. skip-issue-check Indicates that a PR no need to check linked issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant