Skip to content

Split the tools page into explainer and reference pages #325

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jmacdotorg
Copy link
Collaborator

Fixes #305.

@jmacdotorg jmacdotorg requested a review from a team as a code owner May 9, 2025 18:39
@jmacdotorg jmacdotorg requested review from NickBusey and bar0meter May 9, 2025 18:39
Copy link
Contributor

coderabbitai bot commented May 9, 2025

Walkthrough

The changes introduce a new documentation page listing all supported third-party tools, update the existing tools overview page to reference this new list, and modify the sidebar configuration to include the new reference page under the "Supported tools" section.

Changes

File(s) Change Summary
docs/tools/list.md Added a new documentation file listing supported third-party tools with categories and links.
docs/tools/tools.md Revised to remove the tools table, add references to the new list page, and update explanations.
sidebars.ts Updated sidebar to include the new "tools/list" entry under "Supported tools".

Sequence Diagram(s)

sequenceDiagram
    User->>Docs Sidebar: Navigates to "Supported tools"
    Docs Sidebar->>list.md: Displays comprehensive tool list
    User->>tools.md: Reads explainer about OSS tool usage
    tools.md->>list.md: References for full list of tools
Loading

Assessment against linked issues

Objective Addressed Explanation
Split Tools page into explainer and reference pages (#305)
Move reference overview into reference section of ToC (#305)

Poem

In docs we now have quite a list,
Of tools that no one should have missed.
A sidebar hop, a reference hop—
Now finding linters is a breeze, non-stop!
With markdown tables neat and new,
CodeRabbit brings the tools to you.
🐰✨

Tip

⚡️ Faster reviews with caching
  • CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 50a9d8f and a0ce212.

📒 Files selected for processing (3)
  • docs/tools/list.md (1 hunks)
  • docs/tools/tools.md (2 hunks)
  • sidebars.ts (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Cloudflare Pages
🔇 Additional comments (3)
sidebars.ts (1)

136-136: Sidebar update includes new 'Supported tools' reference page

The addition of "tools/list" as the first item under the "Supported tools" category correctly integrates the newly created comprehensive tools list into the navigation. The entry is properly formatted and positioned.

docs/tools/tools.md (2)

6-6: Link to new tools list added

The introductory sentence now directs readers to the dedicated list page via [Supported tools](/tools/list). This aligns with the new documentation structure and provides clear navigation.


45-48: "What's next" section with pointer to detailed list

The new "What's next" section succinctly guides users to the comprehensive list. The heading and bullet are well formatted and maintain consistency with the rest of the page.

✨ Finishing Touches
  • 📝 Generate Docstrings
  • 📝 Generate Unit Tests

🪧 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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 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.
Copy link

Deploying coderabbit-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: a0ce212
Status: ✅  Deploy successful!
Preview URL: https://df1df00d.coderabbit-docs.pages.dev
Branch Preview URL: https://split-tools.coderabbit-docs.pages.dev

View logs

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Inline review comments failed to post. This is likely due to GitHub's limits when posting large numbers of comments. If you are seeing this consistently it is likely a permissions issue. Please check "Moderation" -> "Code review limits" under your organization settings.

Actionable comments posted: 1

🧹 Nitpick comments (4)
docs/tools/list.md (4)

1-4: Frontmatter metadata for new reference page

The YAML frontmatter defines title and description appropriately. Consider adding optional keys such as sidebar_position or slug if you need more control over ordering or the URL, though the current sidebar configuration already ensures correct placement.


6-9: Overview and guidance paragraphs

The opening paragraphs clearly explain the purpose of this reference page and how to navigate it. For brevity and consistency, you may consider tightening the language (e.g., replace "This is a list of the third-party open-source linters..." with "List of third-party linters..."), but the current text is informative.


12-48: Comprehensive tools listing table

The markdown table categorizes each tool clearly. For enhanced usability, you might group tools by category (e.g., separate sub-tables for Code Quality vs. Code Security) or add sorting indicators. Otherwise, this structure effectively conveys the information.


49-75: Link reference definitions

All link reference definitions are present and correctly match the table entries. To improve maintainability, consider alphabetizing these definitions or grouping them by category.

🛑 Comments failed to post (1)
docs/tools/list.md (1)

10-11: ⚠️ Potential issue

Fix link to configuration overview

The link [Configure third-party tools](/tools/) likely does not resolve to the explainer page located at docs/tools/tools.md. It should point to its doc ID tools/tools (i.e., /tools/tools) instead:

- For an overview of how CodeRabbit uses these tools when generating code reviews, as well as general information about controlling their use, see [Configure third-party tools](/tools/).
+ For an overview of how CodeRabbit uses these tools when generating code reviews, as well as general information about controlling their use, see [Configure third-party tools](/tools/tools).
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

For an overview of how CodeRabbit uses these tools when generating code reviews, as well as general information about controlling their use, see [Configure third-party tools](/tools/tools).
🤖 Prompt for AI Agents (early access)
In docs/tools/list.md around lines 10 to 11, the link to the configuration
overview uses an incorrect path `/tools/` which does not resolve to the intended
explainer page. Update the link to use the correct doc ID path `/tools/tools` so
it points to docs/tools/tools.md properly.
@jmacdotorg
Copy link
Collaborator Author

Copy link
Contributor

coderabbitai bot commented May 9, 2025

✅ Actions performed

Reviews paused.

@jmacdotorg
Copy link
Collaborator Author

@coderabbitai resume

Copy link
Contributor

coderabbitai bot commented May 9, 2025

✅ Actions performed

Reviews resumed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants