chore: add CODEOWNERS so reviews must come from the maintainer - #44
Merged
Conversation
With "Require review from Code Owners" on main, an approving review has to be @julia-kafarska's specifically rather than any account with write access. No behaviour change today (sole collaborator), but it keeps the rule true if collaborators are added later. Co-Authored-By: Claude Opus 5 (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
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.
Groundwork for opening the repo to outside contributions.
With Require review from Code Owners enabled on
main, an approving review has to be @julia-kafarska's specifically, rather than any account that happens to have write access. No behaviour change today — you're the sole collaborator — but it keeps "my approval" true if collaborators are ever added, instead of silently degrading to "anyone with write access."The release automation merges with
gh pr merge --admin(scripts/release.mjs), which bypasses this by design, sonpm run releaseis unaffected. That depends onenforce_adminsstayingfalse, which it is.🤖 Generated with Claude Code