Fix CODEOWNERS - Remove invalid usernames causing validation errors #21658
Conversation
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
Co-authored-by: tarunramsinghani <2929463+tarunramsinghani@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix unknown owner errors in repository
Fix CODEOWNERS - Remove invalid usernames causing validation errors
Jan 2, 2026
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.
Context
CODEOWNERS file validation was failing due to 13 invalid GitHub usernames that either don't exist or lack repository write access. This blocks automated ownership assignment and code review routing.
Task Name
N/A - Repository configuration fix
Description
Removed all invalid usernames from
.github/CODEOWNERSacross 32 lines:Individual users removed:
@naziml(2 occurrences) - Azure Container Apps tasks@shilpirachna1(1) - AzureRmWebAppDeploymentV5@menxiao(1) - AzureSpringCloudV0@manos(16) - All test/coverage tasks@vincentdass(2) - Azure deployment common modules@Ajay-MS(1) - VstsAzureRestHelpers_@omeshp,@hiyadav(1) - azure-blobstorage-artifactProvider@kutsen99(6) - Pipeline artifact tasks@ds-ms(2) - GitHubCommentV0, ReviewAppV0@shizhMSFT,@Two-Hearts(1) - NotationV0Team removed:
@Azure/azure-container-registry(1) - NotationV0Affected paths now default to team-level ownership (e.g.,
@microsoft/adoautotest,@microsoft/release-management-task-team) or remaining valid individual owners.Risk Assessment (Low)
Configuration-only change. No code modifications. Ownership falls back to existing team owners.
Change Behind Feature Flag (No)
CODEOWNERS file changes take immediate effect. No runtime behavior changes.
Tech Design / Approach
Documentation Changes Required (No)
Internal GitHub configuration file only.
Unit Tests Added or Updated (No)
Configuration file - no testable code.
Additional Testing Performed
Logging Added/Updated (No)
N/A
Telemetry Added/Updated (No)
N/A
Rollback Scenario and Process (Yes)
Dependency Impact Assessed and Regression Tested (Yes)
Checklist
Original prompt
Unknown owner on line 43: make sure @naziml exists and has write access to the repository …asks/AzureContainerAppsV0/ @naziml @tarunramsinghani Unknown owner on line 45: make sure @naziml exists and has write access to the repository …asks/AzureContainerAppsV1/ @naziml @tarunramsinghani Unknown owner on line 104: make sure @ShilpiRachna1 exists and has write access to the repository …ymentV5/ @jvano @dannysongg @ShilpiRachna1 @microsoft/azure-app-service-pipelines-tasks @microsoft/release-management-task-team @manolerazvan Unknown owner on line 107: make sure @menxiao exists and has write access to the repository … @microsoft/azure-spring-apps @menxiao Unknown owner on line 111: make sure @manos exists and has write access to the repository Tasks/AzureTestPlanV0/ @manos @microsoft/adoautotest Unknown owner on line 145: make sure @vincentdass exists and has write access to the repository …ommon/AzureRmDeploy-common/ @vincentdass @microsoft/release-management-task-team @manolerazvan Unknown owner on line 157: make sure @vincentdass exists and has write access to the repository …Common/VstsAzureHelpers_/ @vincentdass Unknown owner on line 159: make sure @Ajay-MS exists and has write access to the repository …ommon/VstsAzureRestHelpers_/ @Ajay-MS Unknown owner on line 165: make sure @hiyadav exists and has write access to the repository …artifactProvider/ @omeshp @hiyadav Unknown owner on line 165: make sure @omeshp exists and has write access to the repository …obstorage-artifactProvider/ @omeshp @hiyadav Unknown owner on line 167: make sure @manos exists and has write access to the repository …Common/coveragepublisher/ @manos @microsoft/adoautotest Unknown owner on line 231: make sure @kutsen99 exists and has write access to the repository …er @fadnavistanmay @b-barthel @kutsen99 @kunalkaroth Unknown owner on line 233: make sure @kutsen99 exists and has write access to the repository …er @fadnavistanmay @b-barthel @kutsen99 @kunalkaroth Unknown owner on line 235: make sure @kutsen99 exists and has write access to the repository …er @fadnavistanmay @b-barthel @kutsen99 @kunalkaroth Unknown owner on line 253: make sure @DS-MS exists and has write access to the repository Tasks/GitHubCommentV0/ @DS-MS Unknown owner on line 342: make sure @shizhMSFT exists and has write access to the repository …gistry @JeyJeyGao @Two-Hearts @shizhMSFT @tarunramsinghani Unknown owner on line 342: make sure @Two-Hearts exists and has write access to the repository …container-registry @JeyJeyGao @Two-Hearts @shizhMSFT @tarunramsinghani Unknown owner on line 342: make sure the team @Azure/azure-container-registry exists, is publicly visible, and has write access to the repository Tasks/NotationV0/ @Azure/azure-container-registry @JeyJeyGao @Two-Hearts @shizhMSFT @tarunramsinghani Unknown owner on line 388: make sure @manos exists and has write access to the repository …lishCodeCoverageResultsV1/ @manos @microsoft/adoautotest Unknown owner on line 390: make sure @manos exists and has write access to the repository …lishCodeCoverageResultsV2/ @manos @microsoft/adoautotest Unknown owner on line 392: make sure @kutsen99 exists and has write access to the repository …er @fadnavistanmay @b-barthel @kutsen99 @kunalkaroth Unknown owner on line 394: make sure @kutsen99 exists and has write access to the repository …er @fadnavistanmay @b-barthel @kutsen99 @kunalkaroth Unknown owner on line 398: make sure @kutsen99 exists and has write access to the repository …er @fadnavistanmay @b-barthel @kutsen99 @kunalkaroth Unknown owner on line 400: make sure @manos exists and has write access to the repository …asks/PublishTestResultsV1/ @manos @microsoft/adoautotest Unknown owner on line 402: make sure @manos exists and has write access to the repository …asks/PublishTestResultsV2/ @manos @microsoft/adoautotest Unknown owner on line 404: make sure @manos exists and has write access to the repository …/ContainerStructureTestV0/ @manos @microsoft/adoautotest Unknown owner on line 416: make sure @manos exists and has write access to the repository Tasks/QuickPerfTestV1/ @manos @microsoft/adoautotest Unknown owner on line 418: make sure @DS-MS exists and has write access to the repository Tasks/ReviewAppV0/ @DS-MS Unknown owner on line 420: make sure @manos exists and has write access to the repository …asks/RunDistributedTestsV1/ @manos @microsoft/adoautotest Unknown owner on line 422: make sure @manos exists and has write access to the repository …asks/RunJMeterLoadTestV1/ @manos @microsoft/adoautotest Unknown owner on line 424: make sure @manos exists and has write access to the repository Tasks/RunLoadTestV1/ @manos @microsoft/adoautotest Unknown owner on line 460: make sure @manos exists and has write access to the repository Tasks/VsTestV1/ @manos @microsoft/adoautotest Unknown owner on line 462: make sure @manos exists and has write access to the repository Tasks/VsTestV2/ @manos @microsoft/adoautotest Unknown owner on line 464: make sure @manos...
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.