fix: recognize announced repository maintainers as code owners - #157
Open
imran-siddique wants to merge 1 commit into
Open
fix: recognize announced repository maintainers as code owners#157imran-siddique wants to merge 1 commit into
imran-siddique wants to merge 1 commit into
Conversation
Signed-off-by: Imran Siddique <imran.siddique@opaque.co>
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 this changes
The announced maintainers (@carloshvp, @zohebk8s) already have active Maintain access and appear in the approval workflow, but CODEOWNERS excludes them. Add them alongside existing repository owners and record their appointments in MAINTAINERS.md.
The change is confined to ca2a; it grants no organization-team membership and changes no branch rules. Existing owners remain on every rule.
Type of change
Repository ownership and maintainer documentation; no runtime or normative specification change.
Security impact
Adds the announced repository maintainers as eligible code-owner reviewers, including existing general-maintainer alternatives on security-sensitive paths. Preserves current owners and review counts.
Validation
git diff --checkpassed. No runtime tests were run locally because no runtime code changed.Checklist