chore: remove CODEOWNERS - #9
Conversation
The org is not adopting CODEOWNERS. As configured the file was inert: require_code_owner_reviews is false on this repo's branch protection and required_approving_review_count is 0, since CodeRabbit and Greptile do the reviewing -- so it auto-assigned reviewers without gating anything. This was the only module repo carrying one. Removed alongside the org-level copy in .github and the five open PRs proposing the same file, so the org is consistently without it rather than half-adopted.
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
t0kubetsu has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
Warning Review limit reached
Next review available in: 2 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Comment |
1 participant
What
Removes
CODEOWNERS. This was the only module repo carrying one.Why
The org is not adopting CODEOWNERS, and as configured the file was inert:
require_code_owner_reviewsisfalseon this repo's branch protectionrequired_approving_review_countis0— CodeRabbit and Greptile do the reviewingSo it auto-assigned reviewers without gating any merge. Removing it changes no enforcement behaviour.
Scope
Part of one pass: the five open PRs proposing the same file (chainvalidator #2, headersvalidator #3, mailvalidator #3, subdomainenum #2, zoneripper #2) are closed, and the org-level copy in
.githubis removed in its own PR. The org ends up consistently without CODEOWNERS rather than half-adopted.