Skip to content

chore: add CODEOWNERS - #7

Closed
netram-netizen wants to merge 1 commit into
mainfrom
chore/codeowners
Closed

chore: add CODEOWNERS#7
netram-netizen wants to merge 1 commit into
mainfrom
chore/codeowners

Conversation

@netram-netizen

Copy link
Copy Markdown

💡 Summary

Adds .github/CODEOWNERS naming @FeedbackFruits/devops as 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?

  • Owner is @FeedbackFruits/devops because a shared base container image — build/runtime infrastructure.
  • Owner is a team, not an individual: a named person stalls review whenever they are away, and silently goes stale as people change roles. Team membership is already maintained in one place.
  • A single global * 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.
  • Merging this alone changes nothing enforceable. CODEOWNERS only gates merges once branch protection enables Require review from Code Owners; until then it just pre-fills reviewer suggestions. Flipping that switch is deliberately left out of this PR so the reviewer assignment can settle first.
  • @FeedbackFruits/devops does 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.

@netram-netizen
netram-netizen requested a review from a team August 6, 2026 10:06
@netram-netizen

Copy link
Copy Markdown
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.

@netram-netizen
netram-netizen deleted the chore/codeowners branch August 6, 2026 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant