Skip to content

docs fix for self-hosted extension #466

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

Merged
merged 2 commits into from
Jul 22, 2025
Merged

Conversation

ankitjena
Copy link
Contributor

No description provided.

Copy link
Contributor

coderabbitai bot commented Jul 22, 2025

Walkthrough

The documentation for using the VSCode extension with a self-hosted CodeRabbit instance was reorganized for clarity, with improved prerequisites and step-by-step instructions. Additionally, the sidebar configuration was updated to include this revised guide in the appropriate documentation section.

Changes

File(s) Change Summary
docs/guides/use-vscode-selfhosted.md Rewrote and restructured the guide for connecting VSCode to self-hosted CodeRabbit, clarifying prerequisites and instructions.
sidebars.ts Added the updated self-hosted VSCode usage guide to the "Review local changes" section in the sidebar.

Estimated code review effort

1 (~4 minutes)

Possibly related PRs

Poem

🐇
In docs we hop, with steps anew,
Clearer paths for all to view.
Sidebar signs point the way,
To self-hosted lands where coders play.
With every guide, our warren grows—
Onward, where the rabbit goes!

Pre-Merge Checks (1 passed, 2 warnings)

❌ Failed Checks (2 warnings)
Check Name Status Explanation Resolution
Title Check ⚠️ Warning The title 'docs fix for self-hosted extension' is too vague and does not accurately reflect the specific documentation updates to the VSCode self-hosted extension guide. Please revise the pull request title to clearly describe the changes, for example 'docs: clarify VSCode extension setup with self-hosted CodeRabbit guide'.
Description Check ⚠️ Warning The pull request description is empty and does not provide any context, details, or rationale for the documentation changes. Please add a detailed description including a summary of changes, rationale, and any relevant testing instructions, and consider adding a pull request template to standardize future descriptions.
✅ Passed Checks (1 passed)
Check Name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
Impact Analysis

Clarify prerequisites and connection steps in self-hosted VSCode extension guide

ℹ️ Low 📋

The self-hosted VSCode extension guide (docs/guides/use-vscode-selfhosted.md) has been rewritten for clarity: the title was simplified, prerequisites were split into two steps (including an explicit logout requirement), and connection steps were renumbered and reformatted with clearer bulleting and explicit GitHub Enterprise mention. Core instructions remain unchanged.

Ensure that the revised steps accurately reflect the current extension UI and behavior, and verify that any screenshots or links align with the new ordering and formatting.

Preview the updated guide in the documentation site, walk through the end-to-end self-hosted setup, and confirm that each numbered and bulleted step displays correctly and reads unambiguously.

🔍 Related Files
  • docs/guides/use-vscode-selfhosted.md

Add self-hosted VSCode extension guide to documentation sidebar

ℹ️ Low 📋

The sidebar configuration (sidebars.ts) now includes the new “guides/use-vscode-selfhosted” page in the “Review local changes” section, positioned between the existing VSCode guide and the config-VSCode guide.

Verify the sidebar ordering and grouping in both desktop and mobile layouts, and check for any localization or path issues.

Build and navigate the documentation site to confirm the new guide appears in the correct location in the sidebar and links resolve properly.

🔍 Related Files
  • sidebars.ts
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix-self-hosted-extension-docs

🪧 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 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.

@ankitjena ankitjena force-pushed the fix-self-hosted-extension-docs branch from d8e296b to d88fea8 Compare July 22, 2025 06:33
Copy link

cloudflare-workers-and-pages bot commented Jul 22, 2025

Deploying coderabbit-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: 04c45ff
Status: ✅  Deploy successful!
Preview URL: https://6ea9b13e.coderabbit-docs.pages.dev
Branch Preview URL: https://fix-self-hosted-extension-do.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.

Actionable comments posted: 0

🧹 Nitpick comments (5)
sidebars.ts (1)

130-136: Slug naming consistency

All other “self-hosted” documentation pages use the dashed form (self-hosted) in their slugs (self-hosted/github, self-hosted/gitlab, …).
For consistency, consider renaming the new entry to guides/use-vscode-self-hosted (and the underlying file) so that the entire docs tree follows one kebab-case convention.

-				"guides/use-vscode-selfhosted",
+				"guides/use-vscode-self-hosted",
docs/guides/use-vscode-selfhosted.md (4)

1-4: Minor wording/grammar fixes in front-matter

  • The description should use the verb phrase “set up” rather than the noun “setup”.
  • Keeping the full phrase “VS Code extension” in the title helps searchability and consistency with other pages.
-title: Use with self-hosted CodeRabbit
-description: How to setup the VSCode extension with self-hosted CodeRabbit
+title: Use the VS Code extension with self-hosted CodeRabbit
+description: How to set up the VS Code extension with self-hosted CodeRabbit

10-11: Clarify prerequisite wording

  1. “Greater than 0.12.1” excludes 0.12.1 itself. Usually we mean >= 0.12.1.
  2. “Logout” → “Log out” (verb form).
-1. Your extension version should be greater than `0.12.1`.
-2. Logout of the extension if previously logged in.
+1. Ensure the extension version is **`0.12.1` or newer**.
+2. **Log out** of the extension if you were previously signed in.

17-21: Fix typos and provider names

  • Add the missing hyphen in “Self-hosting”.
  • Capitalisation / spelling:
    • “GitLab” (capital L).
    • “Self-hosted GitLab” (hyphen, capital L).
    • “GitHub” (capital H, capital B).
  • Slight wording tweak for bullet 3.
-1. Click on the "Self hosting CodeRabbit?" button, below the "Use CodeRabbit for free" button.
+1. Click the **“Self-hosting CodeRabbit?”** button below **“Use CodeRabbit for free”**.
@@
-3. Select your git provider which you are using with your self-hosted CodeRabbit. (GitLab, Self-Hosted Gitlab, GitHub, GitHub Enterprise)
-   - If using GitHub or GitHub Enterprise, enter your [Github Personal Access Token](...) when prompted.
+3. Select the Git provider used with your self-hosted CodeRabbit instance: **GitLab**, **Self-hosted GitLab**, **GitHub**, or **GitHub Enterprise**.
+   - If you choose GitHub or GitHub Enterprise, enter your [GitHub Personal Access Token](...) when prompted.

23-23: Tone & active voice

Consider an active-voice confirmation to match the rest of the guide.

-You should be connected to your self-hosted instance and ready to use the VSCode extension.
+You’re now connected to your self-hosted instance and ready to use the VS Code extension.
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8a0881f and 04c45ff.

📒 Files selected for processing (2)
  • docs/guides/use-vscode-selfhosted.md (1 hunks)
  • sidebars.ts (1 hunks)
🧠 Learnings (2)
📓 Common learnings
Learnt from: alexcoderabbitai
PR: coderabbitai/coderabbit-docs#0
File: :0-0
Timestamp: 2025-06-02T14:07:49.512Z
Learning: For files in docs/tools/*.md directory: Do not recommend installation instructions or usage setup steps. All tools documented in this directory are pre-installed in CodeRabbit's default environment and require no installation steps from users. Documentation should focus on tool capabilities and features only.
Learnt from: alexcoderabbitai
PR: coderabbitai/coderabbit-docs#176
File: docs/self-hosted/bitbucket.md:37-37
Timestamp: 2024-12-13T15:10:43.483Z
Learning: In the `docs` repository, it's acceptable to use `127.0.0.1` in documentation examples, and CodeRabbit should not flag it as an issue.
docs/guides/use-vscode-selfhosted.md (1)

Learnt from: alexcoderabbitai
PR: coderabbitai/coderabbit-docs#0
File: :0-0
Timestamp: 2025-06-02T14:07:49.512Z
Learning: For files in docs/tools/*.md directory: Do not recommend installation instructions or usage setup steps. All tools documented in this directory are pre-installed in CodeRabbit's default environment and require no installation steps from users. Documentation should focus on tool capabilities and features only.

🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: alexcoderabbitai
PR: coderabbitai/coderabbit-docs#0
File: :0-0
Timestamp: 2025-06-02T14:07:49.512Z
Learning: For files in docs/tools/*.md directory: Do not recommend installation instructions or usage setup steps. All tools documented in this directory are pre-installed in CodeRabbit's default environment and require no installation steps from users. Documentation should focus on tool capabilities and features only.
Learnt from: alexcoderabbitai
PR: coderabbitai/coderabbit-docs#176
File: docs/self-hosted/bitbucket.md:37-37
Timestamp: 2024-12-13T15:10:43.483Z
Learning: In the `docs` repository, it's acceptable to use `127.0.0.1` in documentation examples, and CodeRabbit should not flag it as an issue.
docs/guides/use-vscode-selfhosted.md (1)

Learnt from: alexcoderabbitai
PR: coderabbitai/coderabbit-docs#0
File: :0-0
Timestamp: 2025-06-02T14:07:49.512Z
Learning: For files in docs/tools/*.md directory: Do not recommend installation instructions or usage setup steps. All tools documented in this directory are pre-installed in CodeRabbit's default environment and require no installation steps from users. Documentation should focus on tool capabilities and features only.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Cloudflare Pages

@ankitjena ankitjena merged commit eae7edb into main Jul 22, 2025
4 checks passed
@ankitjena ankitjena deleted the fix-self-hosted-extension-docs branch July 22, 2025 06:41
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