Repository navigation
chore: Finish PublicCandidate triage and gate residual count - #2011
Merged
Merged
Conversation
…2000) Co-authored-by: Cursor <cursoragent@cursor.com>
#2002) Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
…#2005) Co-authored-by: Cursor <cursoragent@cursor.com>
…tion PublicCandidates (#2006) Co-authored-by: Cursor <cursoragent@cursor.com>
…es (#2007) Co-authored-by: Cursor <cursoragent@cursor.com>
…keeps (#2009) Co-authored-by: Cursor <cursoragent@cursor.com>
…2010) Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
|
Warning Review limit reached
Next review available in: 22 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (67)
✨ 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 |
RyanXie123
pushed a commit
to RyanXie123/unity-cli-loop
that referenced
this pull request
Sep 22, 2026
…a#2011) Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes the PublicCandidate triage for issue #1997: scanner accuracy fixes, bucketed deletion/keep decisions, intentional-keep documentation, Newtonsoft
ShouldSerialize*structural keep, and a CI ceiling onPublicCandidatecount.Closes #1997
PublicCandidate progression
Error+ShouldSerialize*ShouldSerialize*keep + PC gate)--max-public-candidates 22High-confidence findings stayed at 0 throughout.
What each PR did
IsExternalInitPackages/srcRuntime asmdefs in production scanError)ShouldSerialize{Property}structurally; add--max-public-candidatesCI gate at 22Intentionally retained PublicCandidates are listed in
docs/dead-code-scanner.md.Out of scope
NativeCliInstallerTests/ToolSkillSynchronizerTestsare tracked as EditMode: NativeCliInstaller progress order and ToolSkillSynchronizer flat-directory detection fail on v3-beta #2001 and are out of scope for this PR.showUnityCliLoopSecuritySettingcarry (plan To-Do 7b) remains a separate follow-up.Test plan
--max-public-candidates 22v3-beta