chore: add CODEOWNERS entry for azure-kubernetes evals - #3046
Merged
Sai Koumudi Kaluvakolanu (saikoumudi) merged 1 commit intoAug 7, 2026
Merged
Conversation
The azure-kubernetes eval suite has no scoped owner, so changes under evals/azure-skills/azure-kubernetes/ fall through to the default `*` owner (@microsoft/github-copilot-for-azure-writers). Because the org ruleset requires code owner review, any PR touching both the skill and its evals needs two separate approvals: an AKS owner for the skill files, plus a writers-team member for the eval files -- even when the eval change is a small fixture that ships with the skill. Mirrors the existing /evals/azure-skills/microsoft-foundry/ entry and uses the same owner list as the azure-kubernetes skill directory.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the repository’s CODEOWNERS configuration to assign explicit code owners for the azure-kubernetes Vally eval suite under evals/azure-skills/azure-kubernetes/, aligning eval ownership with the existing skill ownership and reducing unnecessary review bottlenecks under require_code_owner_review.
Changes:
- Add a scoped CODEOWNERS rule for
/evals/azure-skills/azure-kubernetes/. - Use the same owner set as the existing
/plugins/azure-skills/skills/azure-kubernetes/entry. - Keep eval ownership entries organized within the existing “Plugin skills evals owners (multi-plugin)” block.
Tom Meschter (tmeschter)
approved these changes
Aug 7, 2026
Sai Koumudi Kaluvakolanu (saikoumudi)
approved these changes
Aug 7, 2026
Sai Koumudi Kaluvakolanu (saikoumudi)
merged commit Aug 7, 2026
a12b031
into
microsoft:main
10 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds one line to
.github/CODEOWNERS:Why
The azure-kubernetes eval suite currently has no scoped owner. The only
/evals/entry is formicrosoft-foundry, so everything underevals/azure-skills/azure-kubernetes/falls through to the default*owner, @microsoft/github-copilot-for-azure-writers.Combined with the org ruleset's
require_code_owner_review, that means any PR touching both a skill and its evals needs two separate approvals — an AKS owner for the skill files, plus a writers-team member for the eval files — even when the eval change is a small fixture shipping alongside the skill.#2696 is a live example: 44 skill files approved by an AKS codeowner, blocked on 3 eval fixture files.
Notes
/plugins/azure-skills/skills/azure-kubernetes/entry, so this grants nothing new — the same four people already own the skill these evals cover./evals/azure-skills/microsoft-foundry/pattern.microsoft-foundryline to keep the block alphabetical. The patterns don't overlap, so ordering has no effect on resolution./plugin/skills/block (lines 10–45, pointing at paths deleted in the multi-plugin restructure) is inert and left alone — happy to clean it up separately if wanted.