chore: add CODEOWNERS so code-owner review requirement applies - #92
Merged
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
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
Adds
.github/CODEOWNERSwith@Aleph-Alpha/responses-apias the default owner for the whole repo.The org branch-protection ruleset requires code-owner review on pull requests. With no CODEOWNERS file that requirement matches nothing, so every PR satisfied it vacuously. Listing an owner makes the existing control take effect.
Note: this only works if
@Aleph-Alpha/responses-apihas write access to this repo — GitHub silently ignores owners that don't. Worth confirming before relying on the gate.