Route PR reviews to the DevEx squad via CODEOWNERS#2347
Open
AlexDaines wants to merge 1 commit intodevfrom
Open
Route PR reviews to the DevEx squad via CODEOWNERS#2347AlexDaines wants to merge 1 commit intodevfrom
AlexDaines wants to merge 1 commit intodevfrom
Conversation
AlexDaines
added
Release Not Needed
GarrettBeatty
approved these changes
Apr 24, 2026
philasmar
approved these changes
Apr 24, 2026
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
3 participants
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.
Updates CODEOWNERS to list the DevEx reviewers child team as a co-owner alongside the parent
aws-sdk-dotnet-team. This lets GitHub auto-assign a single squad member as the primary reviewer (via round-robin on the child team) while keeping the parent team as a secondary owner so approvals from any team member still satisfy code-owner review.Context: our team is setting up subteam-based review routing so PRs land on the right squad without losing cross-team visibility. The parent team has no auto-assignment configured; the child team handles round-robin. Either team's approval satisfies the code-owner rule.
Related docs: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners