Skip to content

chore: add CODEOWNERS - #9

Merged
ben-miru merged 1 commit into
mainfrom
chore/codeowners
Oct 21, 2026
Merged

ben-miru merged 1 commit into
mainfrom
chore/codeowners

Conversation

@bens-agent

@bens-agent bens-agent commented Oct 20, 2026 •

Copy link
Copy Markdown
Collaborator

Requested by bens-agent · project thread

Summary

Adds .github/CODEOWNERS making @ben-miru the code owner of every path in this repo.

This is step one of requiring a human approval on every PR. A follow-up PR in mirurobotics/infra (github/terraform/repos.tf) turns on 1 required approval, "require review from Code Owners", and "require approval of the most recent push". Until that lands, this file only auto-requests reviews.

Precedent

No repo in the org has a CODEOWNERS file yet; all repos get the same one-line format.


Generated by Claude Code


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DHfvjCLNmabAiGhEsWgBks
Comment thread .github/CODEOWNERS
@github-actions

Copy link
Copy Markdown

AI review: approve for 1c45a83

This PR adds a single file, .github/CODEOWNERS, which makes @ben-miru the code owner of every path (* @ben-miru). The syntax is valid and there are no correctness or security problems. This is an access-control change. For now it only auto-requests reviews; it becomes a merge gate once the follow-up branch-protection change in mirurobotics/infra lands. I left one non-blocking inline comment: with a single owner, nobody else can approve merges when they're away, so a backup owner or team would help. Also, GitHub ignores code owners without write access, so @ben-miru's access should be checked before enforcement is turned on. There were no earlier review threads.

Review run

@ben-miru
ben-miru merged commit 814ce16 into main Oct 21, 2026
2 checks passed
@ben-miru
ben-miru deleted the chore/codeowners branch October 21, 2026 01:09
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.

3 participants