chore: add CODEOWNERS for the maintainers team - #148
Merged
Conversation
Every pull request now automatically requests a review from @ROCm/rocm-cli-maintainers, so review requests no longer depend on the author remembering to pick someone. Signed-off-by: Roman Inflianskas <Roman.Inflianskas@amd.com>
volen-silo
approved these changes
Jul 29, 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
2 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.
Pull requests currently get a reviewer only if the author remembers to pick one.
Adds
.github/CODEOWNERSwith a single catch-all entry pointing at@ROCm/rocm-cli-maintainers, so GitHub requests a review from the maintainers team on every pull request.Two supporting changes were made on the repo settings side, since a CODEOWNERS entry is inert without them:
rocm-cli-maintainersteam had no access to this repository, which would have made the entry an invalid owner — it now has write access;mainbranch protection will require an approval from a code owner once this lands.Reviewer membership is managed through the team, not this file.