Repository navigation
OTTER-681: Add CODEOWNERS - #81
Merged
Merged
Conversation
rnathuji
approved these changes
Oct 20, 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Makes
@safeinsights/shotter-devsthe code owner for every path, as part of the Segregation of Duties work in OTTER-681. The file is the same as the one in safeinsights/management-app#1209.GitHub does not let the author's own team membership satisfy a team owner, so another shotter-devs member must review each PR. I did not use
all-devs, because it contains bot accounts.The org
require-prruleset now hasrequire_code_owner_reviewon, so this takes effect when the PR merges.