chore: add CODEOWNERS to route PR reviews#2
Conversation
Adds @nmbrthirteen as default code owner for every path. Future trusted contributors will be added alongside, and the branch protection rule for main will be updated to require code-owner approval once a second maintainer exists.
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Summary
Adds `.github/CODEOWNERS` with @nmbrthirteen as the default owner for every path.
GitHub will now auto-request review from listed code owners whenever a PR touches matching files.
Why
Sets up the open-source contribution model:
When a trusted contributor is promoted later, adding them to this file (and granting Write access in repository settings) makes them an additional valid reviewer — no other plumbing needed.
Follow-up (not in this PR)
When a second maintainer joins, bump branch protection:
```bash
gh api repos/nmbrthirteen/podcli/branches/main/protection/required_pull_request_reviews \
-X PATCH -f required_approving_review_count=1 -F require_code_owner_reviews=true
```
That makes code-owner approval mandatory for every merge.
Test plan