chore: add CODEOWNERS - #7
Closed
netram-netizen wants to merge 1 commit into
Closed
Conversation
netram-netizen
force-pushed
the
chore/codeowners
branch
from
August 6, 2026 09:28
2fb56db to
ddb6ce3
Compare
Author
|
Closing: CODEOWNERS auto-requests review from the whole owning team on every PR, with no document-only mode. That fan-out is more notification noise than the ownership signal is worth. Ownership is being recorded centrally in feedbackfruits-devsecops instead. |
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.
💡 Summary
Adds
.github/CODEOWNERSnaming@FeedbackFruits/devopsas the default owner for every path in this repo. No repo in the devsecops scope had a CODEOWNERS file, so review requests have been going to whoever the author happened to pick, and there was no recorded answer to who owns this code.🛠️ What does this PR do?
@FeedbackFruits/devopsbecause a shared base container image — build/runtime infrastructure.*rule rather than per-path ownership — this repo has no subtree with a genuinely different owner, and a one-line file stays correct as the tree moves.@FeedbackFruits/devopsdoes not have write access to this repo yet, and GitHub will mark the entry invalid until it does. The grant is being handled separately — do not merge before it lands.