chore(codeowners): add ragnorc as engineering owner

This commit is contained in:
Ragnor Comerford 2026-05-28 11:20:51 +02:00
parent 4de490c10c
commit 972a6e047b
No known key found for this signature in database
3 changed files with 5 additions and 4 deletions

4
.github/CODEOWNERS vendored
View file

@ -8,9 +8,9 @@
# CI fails if this file drifts from its source, and rejects PRs that
# edit this file directly without also editing the yml.
* @aaltshuler
* @aaltshuler @ragnorc
crates/** @aaltshuler
crates/** @aaltshuler @ragnorc
docs/** @aaltshuler @ragnorc
README.md @aaltshuler @ragnorc
AGENTS.md @aaltshuler @ragnorc

View file

@ -19,9 +19,10 @@ roles:
engineering:
description: >
All production code under crates/**. Engine, CLI, server,
compiler. Single owner; review must come from this person.
compiler. Either named member can approve.
members:
- aaltshuler
- ragnorc
docs:
description: >

View file

@ -8,7 +8,7 @@ This setup gives every role change a reviewable PR and a permanent in-repository
| Role | Members | Scope |
|---|---|---|
| `engineering` | `@aaltshuler` | All code under `crates/**`, repository infrastructure, default for unmapped paths |
| `engineering` | `@aaltshuler`, `@ragnorc` | All code under `crates/**`, repository infrastructure, default for unmapped paths |
| `docs` | `@aaltshuler`, `@ragnorc` | `docs/**`, README.md, AGENTS.md, CLAUDE.md, SECURITY.md |
GitHub treats multiple owners in a CODEOWNERS line as **"any one of them satisfies the review requirement"**. For docs, either named member can approve. To require N distinct approvers on a specific path, layer a CI check on top (not currently configured).