yiguolei opened a new pull request, #70241:
URL: https://github.com/apache/doris/pull/70241

   ### Background
   
   GitHub uses `.github/CODEOWNERS` to select code owners for changed paths. 
The file has no ownership rules for BE core and common, and still lists two 
paths that no longer exist.
   
   ### What problem does this PR solve?
   
   Issue Number: None
   Related PR: None
   PR Type: Build/CI/Chore
   
   Problem Summary:
   
   Assign `@yiguolei` and `@Mryange` as code owners for `be/src/core` and 
`be/src/common`. Remove the stale FE `fsv2` and BE 
`olap/rowset/segment_v2/variant` rules.
   
   ### Details
   
   - **Affected:** `.github/CODEOWNERS` only; two rules added and two removed.
   - **Developer and release impact:** Updates ownership for BE core/common 
changes and removes rules for nonexistent paths. No Doris runtime behavior 
changes.
   - **License and third-party:** None.
   - **Rollback:** Revert the CODEOWNERS changes.
   
   ### Testing
   
   - `git diff --check` passed locally.
   - Validated all 148 remaining rules against Git-tracked files; every rule 
matches.
   - Verified the effective core/common rules list exactly `@yiguolei @Mryange`.
   - No build or runtime tests run because this only changes GitHub ownership 
metadata.
   
   ### Release note
   
   None.
   
   ### Check List (For Author)
   
   - Behavior changed: No
   - Does this need documentation: No
   - Pre-submission status: Ready
   
   ### AI Disclosure
   
   - Tool: OpenAI Codex.
   - Generated: CODEOWNERS changes and this description.
   - Human review: Pending.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to