Skip to content

Add knowledge base feature flag defns in self hosted docs #469

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

ganeshpatro321
Copy link
Contributor

No description provided.

Copy link
Contributor

coderabbitai bot commented Jul 22, 2025

Walkthrough

The documentation for self-hosted integrations with Azure DevOps, Bitbucket, GitHub, and GitLab was updated to restructure the environment variable configuration for knowledge base features. A single flag was replaced with a global feature flag and multiple granular flags, providing detailed control over knowledge base indexing options. No code or public API changes occurred.

Changes

Files Change Summary
docs/self-hosted/azure-devops.md,
docs/self-hosted/bitbucket.md,
docs/self-hosted/github.md,
docs/self-hosted/gitlab.md
Updated environment variable documentation: replaced ENABLE_LEARNINGS with ENABLE_KNOWLEDGE_BASE and granular flags for knowledge base features; clarified OBJECT_STORE_URI requirement.

Estimated code review effort

1 (~5 minutes)

Poem

In docs we hopped with nimble feet,
New flags for knowledge, oh so neat!
From one big switch to many small,
Now you can finely tune them all.
OBJECT_STORE_URI stands proud and tall—
A rabbit’s guide for one and all!
🐇✨

Pre-Merge Checks (1 passed, 2 warnings)

❌ Failed Checks (2 warnings)
Check Name Status Explanation Resolution
Title Check ⚠️ Warning The title uses an unclear abbreviation 'defns' and lacks clarity and specificity about what is being changed in the self-hosted documentation. Revise the pull request title to avoid abbreviations and clearly describe the change, for example: 'docs(self-hosted): Add knowledge base feature flag definitions'.
Description Check ⚠️ Warning The pull request description is empty and does not provide any context, summary, or rationale for the documentation changes. Add a detailed description that outlines the changes across all self-hosted docs (Azure DevOps, Bitbucket, GitHub, GitLab), explains the new global and granular feature flags, provides the rationale for these updates, and consider adding a pull request template to the repository to ensure completeness.
✅ Passed Checks (1 passed)
Check Name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch kb-selfhosted

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

Copy link

Deploying coderabbit-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: 19232c8
Status: ✅  Deploy successful!
Preview URL: https://ce1c0dee.coderabbit-docs.pages.dev
Branch Preview URL: https://kb-selfhosted.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

🔭 Outside diff range comments (1)
docs/self-hosted/github.md (1)

164-168: Outdated reference to removed flag

The note still says:

- When ENABLE_LEARNINGS is set to true, …

ENABLE_LEARNINGS no longer exists. Replace with the new pair:

- When ENABLE_KNOWLEDGE_BASE=true and ENABLE_LEARNING_INDEX=true, …

This avoids confusing readers who will look for the old flag.

🧹 Nitpick comments (4)
docs/self-hosted/bitbucket.md (1)

19-20: Minor grammar nit ‑ remove extraneous “s”

“… profile picture to ensures easy recognition.”

Change to “… profile picture to ensure easy recognition.”

docs/self-hosted/github.md (1)

45-46: Grammar nit – “to ensure”

Same wording issue as in other guides:

“… logo … as the profile picture to ensures easy recognition.”

Use “to ensure”.

docs/self-hosted/azure-devops.md (1)

19-20: Grammar nit – “to ensure”

“… profile picture to ensures easy recognition.”

Replace “ensures” with “ensure”.

docs/self-hosted/gitlab.md (1)

19-20: Grammar nit – “to ensure”

“… profile picture to ensures easy recognition.”

Use “to ensure”.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between eae7edb and 19232c8.

📒 Files selected for processing (4)
  • docs/self-hosted/azure-devops.md (1 hunks)
  • docs/self-hosted/bitbucket.md (1 hunks)
  • docs/self-hosted/github.md (1 hunks)
  • docs/self-hosted/gitlab.md (1 hunks)
🧠 Learnings (4)
docs/self-hosted/azure-devops.md (1)

Learnt from: aravindputrevu
PR: #402
File: docs/guides/setup-best-practices.md:21-21
Timestamp: 2025-06-18T09:22:07.198Z
Learning: The word "CodeRabbit" should always have both C and R capitalized (not "coderabbit", "Coderabbit", or "CoderabbitAI"). The correct format is "CodeRabbit" and "CodeRabbitAI" for the service account. Proactively correct this capitalization in review comments when contributors mistype it.

docs/self-hosted/bitbucket.md (1)

Learnt from: aravindputrevu
PR: #402
File: docs/guides/setup-best-practices.md:21-21
Timestamp: 2025-06-18T09:22:07.198Z
Learning: The word "CodeRabbit" should always have both C and R capitalized (not "coderabbit", "Coderabbit", or "CoderabbitAI"). The correct format is "CodeRabbit" and "CodeRabbitAI" for the service account. Proactively correct this capitalization in review comments when contributors mistype it.

docs/self-hosted/gitlab.md (1)

Learnt from: aravindputrevu
PR: #402
File: docs/guides/setup-best-practices.md:21-21
Timestamp: 2025-06-18T09:22:07.198Z
Learning: The word "CodeRabbit" should always have both C and R capitalized (not "coderabbit", "Coderabbit", or "CoderabbitAI"). The correct format is "CodeRabbit" and "CodeRabbitAI" for the service account. Proactively correct this capitalization in review comments when contributors mistype it.

docs/self-hosted/github.md (3)

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: #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.

Learnt from: aravindputrevu
PR: #402
File: docs/guides/setup-best-practices.md:21-21
Timestamp: 2025-06-18T09:22:07.198Z
Learning: The word "CodeRabbit" should always have both C and R capitalized (not "coderabbit", "Coderabbit", or "CoderabbitAI"). The correct format is "CodeRabbit" and "CodeRabbitAI" for the service account. Proactively correct this capitalization in review comments when contributors mistype it.

🧰 Additional context used
🧠 Learnings (4)
docs/self-hosted/azure-devops.md (1)

Learnt from: aravindputrevu
PR: #402
File: docs/guides/setup-best-practices.md:21-21
Timestamp: 2025-06-18T09:22:07.198Z
Learning: The word "CodeRabbit" should always have both C and R capitalized (not "coderabbit", "Coderabbit", or "CoderabbitAI"). The correct format is "CodeRabbit" and "CodeRabbitAI" for the service account. Proactively correct this capitalization in review comments when contributors mistype it.

docs/self-hosted/bitbucket.md (1)

Learnt from: aravindputrevu
PR: #402
File: docs/guides/setup-best-practices.md:21-21
Timestamp: 2025-06-18T09:22:07.198Z
Learning: The word "CodeRabbit" should always have both C and R capitalized (not "coderabbit", "Coderabbit", or "CoderabbitAI"). The correct format is "CodeRabbit" and "CodeRabbitAI" for the service account. Proactively correct this capitalization in review comments when contributors mistype it.

docs/self-hosted/gitlab.md (1)

Learnt from: aravindputrevu
PR: #402
File: docs/guides/setup-best-practices.md:21-21
Timestamp: 2025-06-18T09:22:07.198Z
Learning: The word "CodeRabbit" should always have both C and R capitalized (not "coderabbit", "Coderabbit", or "CoderabbitAI"). The correct format is "CodeRabbit" and "CodeRabbitAI" for the service account. Proactively correct this capitalization in review comments when contributors mistype it.

docs/self-hosted/github.md (3)

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: #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.

Learnt from: aravindputrevu
PR: #402
File: docs/guides/setup-best-practices.md:21-21
Timestamp: 2025-06-18T09:22:07.198Z
Learning: The word "CodeRabbit" should always have both C and R capitalized (not "coderabbit", "Coderabbit", or "CoderabbitAI"). The correct format is "CodeRabbit" and "CodeRabbitAI" for the service account. Proactively correct this capitalization in review comments when contributors mistype it.

⏰ 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). (2)
  • GitHub Check: test
  • GitHub Check: Cloudflare Pages
🔇 Additional comments (3)
docs/self-hosted/bitbucket.md (1)

118-130: Flag name & pluralization inconsistency

ENABLE_LEARNING_INDEX is singular, whereas the previous flag (ENABLE_LEARNINGS) and the product wording (“Learnings”) are plural. Double-check the actual variable expected by the agent; if the backend still looks for ENABLE_LEARNINGS_INDEX (plural) this doc will drift out of sync and mislead deployers.
If the new singular form is intentional, ensure all four self-hosted guides and the codebase use the exact same spelling.

docs/self-hosted/azure-devops.md (1)

148-150: Contradictory guidance on optional values

The line states:

- Values marked with [] are not optional to provide.

Square brackets are used throughout the docs to denote optional fields (e.g. [<openai-base-url>]). Saying they are “not optional” contradicts that convention and will confuse operators. Clarify whether the bracketed variables are optional or mandatory and update wording accordingly.

docs/self-hosted/gitlab.md (1)

190-192: Contradictory guidance on optional values

Same issue as Azure DevOps guide – brackets indicate optional fields, but the note claims they are “not optional”. Re-align the note with the established bracket convention.

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.

2 participants