docs: clarify PR review eligibility (#378)

[hardikkgupta]

Adds "Review eligibility" section to clarify which PRs CodeRabbit reviews.

Tackles #378

[coderabbitai]

Walkthrough

A new "Review eligibility" section was added to the documentation, detailing when CodeRabbit reviews pull requests for public and private repositories. The section introduces the ProPlanNotice component to display information about the Pro plan. No changes were made to exported or public entities.

Changes

File(s)	Change Summary
docs/guides/code-review-overview.md	Added "Review eligibility" section; clarified review conditions for public/private repositories; imported and embedded ProPlanNotice component.

Poem

In the docs a section grew,
Explaining when reviews come through.
Public? All get a look,
Private? Pro plan’s in the book.
With ProPlanNotice shining bright,
Eligibility is now in sight—
CodeRabbit hops with pure delight! 🐇✨

✨ Finishing Touches

🧪 Generate Unit Tests

• Create PR with Unit Tests
• Commit Unit Tests in branch docs/clarify-review-eligibility
• Post Copyable Unit Tests in Comment

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai auto-generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (3)

docs/guides/code-review-overview.md (3)

19-19: Consider clarifying section title
You might rename this heading to ## Pull request review eligibility for explicitness and consistency with other multi-PR contexts.

---

21-25: Remove unnecessary Markdown line-breaks
The trailing two spaces on the first bullet item force an in-list line break, which isn't needed here. Removing them simplifies the markup without altering rendering.

---

26-26: Evaluate placement of ProPlanNotice
If the notice is intended to highlight private-repo requirements specifically, consider embedding it within that bullet or wrapping it in an admonition for clearer context.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 94f88f3 and 47446e5.

📒 Files selected for processing (1)

• docs/guides/code-review-overview.md (2 hunks)

🔇 Additional comments (1)

docs/guides/code-review-overview.md (1)

7-7: Verify MDX import in .md file
Ensure that Docusaurus is configured to process MDX imports in .md-suffixed docs. If not, consider renaming this file to .mdx. Also confirm that @site/src/components/ProPlanNotice.mdx exists at the specified path.