Skip to content

docs(agents): code-owner gates disabled org-wide until multiple maintainers exist - #208

Open
seonghobae wants to merge 4 commits into
masterfrom
cwl/codeowner-policy-note
Open

docs(agents): code-owner gates disabled org-wide until multiple maintainers exist#208
seonghobae wants to merge 4 commits into
masterfrom
cwl/codeowner-policy-note

Conversation

@seonghobae

Copy link
Copy Markdown
Collaborator

Records the 2026-08-04 org policy in AGENTS.md: code-owner review requirements are disabled everywhere (solo maintainer cannot satisfy them). ON HOLD until the org has multiple maintainers — do not re-enable.

@coderabbitai

coderabbitai Bot commented Aug 4, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 40 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: c9e85ef1-c674-4f8f-8302-1d4e844abbea

📥 Commits

Reviewing files that changed from the base of the PR and between 35e4498 and 38a53ac.

📒 Files selected for processing (2)
  • .github/workflows/r.yml
  • AGENTS.md

Comment @coderabbitai help to get the list of available commands.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@seonghobae

Copy link
Copy Markdown
Collaborator Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Aug 4, 2026

Copy link
Copy Markdown
✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@seonghobae

Copy link
Copy Markdown
Collaborator Author

@coderabbitai approve

@coderabbitai

coderabbitai Bot commented Aug 4, 2026

Copy link
Copy Markdown
✅ Action performed

Comments resolved. Approval is disabled; enable reviews.request_changes_workflow to allow explicit top-level @coderabbitai resolve or @coderabbitai approve commands.

Seongho Bae and others added 2 commits August 4, 2026 13:46
…arallel 6.2

The check job fails building SimDesign because the P3M stringfish binary
references legacy tbb::internal symbols removed from the oneTBB shipped
by the newly released RcppParallel 6.2.0 (undefined symbol
_ZN3tbb8internal25concurrent_vector_base_v316internal_grow_by...).
Forcing cran::stringfish?source makes pak compile it against the
installed RcppParallel so the symbols match.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The cran::stringfish?source ref did not stick (pak resolves the
transitive dep to the P3M binary), and here the broken binary kills the
SimDesign source build inside setup-r-dependencies itself, so the
rebuild must run before that step. Pre-install Rcpp/RcppParallel, then
build stringfish from cloud.r-project.org source (P3M serves binaries
even through its source API); pak keeps the installed same-version copy.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.

1 participant