Repository navigation
{Misc} Rename CODEOWNERS to OWNERS - #10496
Conversation
There was a problem hiding this comment.
🟡 Changes recommended
The ownership verifier still opens the deleted file and will fail when run.
1 open issue
What changed in this PR
Moves ownership information to a normal file to support squad-based reviews without GitHub’s built-in CODEOWNERS behavior.
Changes:
- Replaces
.github/CODEOWNERSwith.github/OWNERS. - Updates many ownership entries to squad teams.
| File | Description |
|---|---|
.github/OWNERS |
Retains ownership information with updated squad assignments. |
.github/CODEOWNERS |
Removes GitHub’s recognized ownership file. |
Review effort: Balanced
| @@ -0,0 +1,349 @@ | |||
| # See for instructions on this file https://help.github.com/articles/about-codeowners/ | |||
There was a problem hiding this comment.
@Azure/x-engineering-agent Update verifier and README to use .github/OWNERS
The rename leaves scripts/ci/verify_codeowners.py:14–20 opening .github/CODEOWNERS, so running the verifier raises FileNotFoundError instead of checking ownership. Update it to read .github/OWNERS. Also update README.md:32, which still tells contributors to add owners to the old path; following that instruction could recreate the file and restore GitHub's automatic review behavior.
|
Misc |
X Engineering Agent ReportReview — Comments Copilot's stale-path feedback is addressed: the verifier and README now reference P2 — Restore omitted ownership entries. The supplied upstream CI snapshot reports no failures; I did not rerun CI, execute the verifier, or verify GitHub review-routing behavior. Test validation
Risk assessment — 3/100 · LowThe Low rating reflects the detected change scope with no elevated security, reliability, customer, operational, dependency, sovereign-cloud, generated-output, or cross-component signal.
Posted by x-engineering-agent (Reviewer) |

🤖 PR Validation — ️✔️ All clear
Why do we rename CODEOWNERS to OWNERS?
As we move to a squad-based Scrum Master model, CODEOWNERS has become a bottleneck for code review productivity.
After we renamed CODEOWNERS to OWNERS, GitHub will then treat it (OWNERS) as a normal file, so we can keep the ownership information without triggering the built-in CODEOWNERS behavior (Merging will be blocked by owner's approval).
This also prevents GitHub from automatically requesting reviews from the listed owners, which no longer matches our process. Instead, the squad, acting as the Scrum Master, should be assigned as the reviewer.