Repository navigation
owners: remove develop docs aliases (#24543) - #24544
ti-chi-bot[bot] merged 2 commits into
Conversation
Signed-off-by: ti-chi-bot <ci@pingcap.com>
|
@lilin90 This PR has conflicts, I have hold it. |
|
@ti-chi-bot: ## If you want to know how to resolve it, please read the guide in TiDB Dev Guide. DetailsInstructions 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. |
|
The content of OWNERS_ALIASES is invalid. |
📝 Walkthrough
Merge Risk: 🟡 Moderate · up to
|
There was a problem hiding this comment.
Actionable comments posted: 3
ℹ️ Review info
⚙️ Run configuration
- Source mode: Auto
- Repository: pingcap/docs
- Branch: release-8.5
- File: .coderabbit.yaml
- Commit: 139d983
- Layers: Repository YAML
- Review profile: ASSERTIVE
- Plan: Advanced
- Run ID:
53d10d22-7b99-47d6-82d3-261c9bb06a75
📒 Files selected for processing: 2
OWNERS_ALIASESdevelop/OWNERS
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lilin90 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to GitHub limitations.
🟡 Minor · Remove the sig-develop-docs-reviewers alias definition instead of replacing… · OWNERS_ALIASES:5
OWNERS_ALIASES:5
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winRemove the
sig-develop-docs-reviewersalias definition instead of replacing its member.The PR removes the obsolete
sig-develop-docs-reviewersconfiguration. At the reviewed head, this alias is still defined and maps toseominjea1942. This keeps a reviewer group that the PR is meant to remove, so the review routing fordevelop/changes can still include that account. Delete the definition. Thedevelop/OWNERSreviewers reference is a separate correction and is not covered here.Suggested fix
aliases: sig-develop-docs-approvers: - seominjea1942 - sig-develop-docs-reviewers: - - seominjea1942 sig-community-reviewers:
ℹ️ Review info
⚙️ Run configuration
- Source mode: Auto
- Repository: pingcap/docs
- Branch: release-8.5
- File: .coderabbit.yaml
- Commit: 139d983
- Layers: Repository YAML
- Review profile: ASSERTIVE
- Plan: Advanced
- Run ID:
f07a55d0-1914-442e-a807-d8bd0d75f924
📒 Files selected for processing: 1
OWNERS_ALIASES
💤 Files with no reviewable changes: 1
- OWNERS_ALIASES
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 1 remain after this review.
This is an automated cherry-pick of #24543
What is changed, added, or deleted? (Required)
Remove the obsolete
sig-develop-docs-approversandsig-develop-docs-reviewersconfiguration fromdevelop/OWNERSandOWNERS_ALIASES. Keep thearea/developautomatic label configuration.Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
AI agent involvement
Do your changes match any of the following descriptions?
Summary by CodeRabbit