chore: route code-owner reviews to @knowledgestack/ks-admins#3
Merged
Conversation
Replaces the invalid @ARNAVGOEL code-owner (not an org member) with the newly created ks-admins team. Branch protection on main requires code-owner approval, so every PR will now auto-request review from the team. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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
Replaces the invalid
@arnavgoelcode-owner entry (not a real GitHub account) with the newly created @knowledgestack/ks-admins team.Team setup
ks-adminsarnav2(maintainer),frankgu968(maintainer)maintainonknowledgestack/ks-cookbookBranch-protection changes on
mainrequire_code_owner_reviews: true— every PR now requires approval from ks-admins.enforce_admins: false— org owners (@arnav2 and @frankgu968) can bypass the review requirement when needed.Everything else stays the same: 1 approving review required, 2 CI status checks, no force-pushes, no branch deletion, conversation resolution required.
Test plan
🤖 Generated with Claude Code