Skip to content

Update mkdocs.yml to include Semantic Caching Tool#44

Merged
dpage merged 1 commit intomainfrom
susan-pg_semantic_cache
Mar 25, 2026
Merged

Update mkdocs.yml to include Semantic Caching Tool#44
dpage merged 1 commit intomainfrom
susan-pg_semantic_cache

Conversation

@susan-pgedge
Copy link
Copy Markdown
Member

@susan-pgedge susan-pgedge commented Feb 24, 2026

Removed several pgEdge tools and added Semantic Caching Tool with versioning.

Summary by CodeRabbit

  • Documentation
    • Added a new Community Extension "pg_semantic_cache" to docs with versioned releases and a top-level navigation entry.
  • Improvements
    • Enhanced versioned-docs auto-detection and navigation to surface the new extension and its releases more reliably.
  • Chores
    • Ignored the generated documentation entry for the new extension in repository ignore rules.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Feb 24, 2026

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 086cda24-9130-46ea-b564-0810948a93b2

📥 Commits

Reviewing files that changed from the base of the PR and between 43a7774 and f48baa6.

📒 Files selected for processing (3)
  • .gitignore
  • docs/index.md
  • mkdocs.yml
 ________________________________________________________________
< KōdoUsagi Gundam is my Japanese cousin. He's a bit more mecha. >
 ----------------------------------------------------------------
  \
   \   (\__/)
       (•ㅅ•)
       /   づ

Walkthrough

Adds the pg_semantic_cache community extension as a versioned external docset: updates mkdocs.yml nav and versioned_docsets, adds a docs/index.md entry for pg-semantic-cache/, and ignores the generated redirect file in .gitignore.

Changes

Cohort / File(s) Summary
Docsite configuration & navigation
mkdocs.yml
Registered pg-semantic-cache in extra.versioned_docsets, added pg_semantic_cache under extra.nav_categories.Database (Community Extensions), and added a top-level nav entry importing pg-semantic-cache docs for v0.1.0-beta4 and main. Review mkdocs import syntax and nav order.
Docs index
docs/index.md
Inserted a new pg_semantic_cache item under Database → Community Extensions linking to pg-semantic-cache/.
Ignored generated docs
.gitignore
Added docs/pg-semantic-cache/index.md to ignore list for generated/imported docset redirect files. Verify path matches generated outputs.

Sequence Diagram(s)

sequenceDiagram
    participant Dev as Developer / PR
    participant Mk as MkDocs Build
    participant Repo as External Repo (pg-semantic-cache)
    participant Local as Local docs/ (imported)
    participant VCS as Git / .gitignore

    Dev->>Mk: update mkdocs.yml (versioned_docsets, nav)
    Mk->>Repo: import docs from repo branches (v0.1.0-beta4, main)
    Repo-->>Mk: serve imported files (docs/pg-semantic-cache/)
    Mk->>Local: place imported files under docs/pg-semantic-cache/
    Dev->>VCS: add .gitignore entry for docs/pg-semantic-cache/index.md
    VCS-->>Local: prevents committed generated redirect file
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • AntTheLimey
🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly describes the main change: adding the Semantic Caching Tool to mkdocs.yml. It is concise, specific, and accurately reflects the primary modification across all affected files.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch susan-pg_semantic_cache

Comment @coderabbitai help to get the list of available commands and usage tips.

@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages bot commented Feb 24, 2026

Deploying pgedge-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: 8beb111
Status: ✅  Deploy successful!
Preview URL: https://4423911f.pgedge-docs.pages.dev
Branch Preview URL: https://susan-pg-semantic-cache.pgedge-docs.pages.dev

View logs

@susan-pgedge susan-pgedge requested a review from dpage February 24, 2026 15:28
Copy link
Copy Markdown

@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: 1

🧹 Nitpick comments (1)
mkdocs.yml (1)

445-447: Consider adding an "Early Development" warning for this beta tool in docs/index.md.

This tool is at v0.1.0-beta4, the same maturity level as the AI Toolkit tools (RAG Server, MCP Server, etc.) which are all covered by the "Early Development" admonition in docs/index.md. Since pg-semantic-cache is also in an early beta state and semantically adjacent to the AI toolkit, it may benefit from a similar warning to set appropriate user expectations.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@mkdocs.yml` around lines 445 - 447, Add an "Early Development" admonition for
the Semantic Caching Tool in docs/index.md: locate the section or heading that
documents "Semantic Caching Tool" (matching the mkdocs nav entry "Semantic
Caching Tool" and its v0.1.0-beta4/Development variants) and insert the same
Early Development warning used for the AI Toolkit tools (RAG Server, MCP Server,
etc.), making clear the beta status and guidance for users; keep wording
consistent with the existing admonition formatting and placement so the warning
appears next to the Semantic Caching Tool entry.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@mkdocs.yml`:
- Line 130: The version slug and nav titles are inconsistent: change the
versioned_docsets entry currently named "pg_semantic_cache" to
"semantic-caching-tool", update the corresponding nav_categories title
(currently "pg_semantic_cache") to the human-readable "Semantic Caching Tool"
(and ensure its URL uses "semantic-caching-tool/"), and keep the nav entry title
as "Semantic Caching Tool" so overrides/main.html's slugify(doc title) will
equal the docset_slug; in short, make the versioned_docsets identifier, the
nav_categories url slug, and the slugified nav title all "semantic-caching-tool"
so the dropdown and nav-category links resolve.

---

Nitpick comments:
In `@mkdocs.yml`:
- Around line 445-447: Add an "Early Development" admonition for the Semantic
Caching Tool in docs/index.md: locate the section or heading that documents
"Semantic Caching Tool" (matching the mkdocs nav entry "Semantic Caching Tool"
and its v0.1.0-beta4/Development variants) and insert the same Early Development
warning used for the AI Toolkit tools (RAG Server, MCP Server, etc.), making
clear the beta status and guidance for users; keep wording consistent with the
existing admonition formatting and placement so the warning appears next to the
Semantic Caching Tool entry.

ℹ️ Review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 25877e4 and e4d3712.

📒 Files selected for processing (2)
  • docs/index.md
  • mkdocs.yml

Copy link
Copy Markdown

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

🧹 Nitpick comments (1)
hooks/versioned_redirects.py (1)

26-31: Consider validating that slug is non-empty for dict entries.

If a dict entry is missing the slug key or has an empty value, docset.get('slug', '') returns an empty string. This would cause docset_dir to resolve to docs_dir itself, potentially writing redirect content to docs/index.md.

💡 Suggested defensive check
         # Support both string entries and {slug, nav_title} dict entries
         if isinstance(docset, str):
             docset_slug = docset
         else:
             docset_slug = docset.get('slug', '')
+        if not docset_slug:
+            log.warning(f"Skipping docset entry with empty slug: {docset}")
+            continue
         docset_dir = os.path.join(docs_dir, docset_slug)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@hooks/versioned_redirects.py` around lines 26 - 31, The code currently sets
docset_slug = docset.get('slug', '') which can be empty and cause docset_dir to
resolve to docs_dir; update the logic in the block handling dict-type docset
entries (the docset variable and docset_slug computation in
hooks/versioned_redirects.py) to validate that the slug exists and is non-empty:
if missing or blank, either log an error and skip processing that entry or raise
an explicit exception (e.g., ValueError) so you never join an empty slug into
docs_dir; ensure any downstream use of docset_dir only occurs when docset_slug
is a valid non-empty string.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@hooks/versioned_redirects.py`:
- Around line 26-31: The code currently sets docset_slug = docset.get('slug',
'') which can be empty and cause docset_dir to resolve to docs_dir; update the
logic in the block handling dict-type docset entries (the docset variable and
docset_slug computation in hooks/versioned_redirects.py) to validate that the
slug exists and is non-empty: if missing or blank, either log an error and skip
processing that entry or raise an explicit exception (e.g., ValueError) so you
never join an empty slug into docs_dir; ensure any downstream use of docset_dir
only occurs when docset_slug is a valid non-empty string.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: cd65e69b-e085-41bc-86de-30026297919e

📥 Commits

Reviewing files that changed from the base of the PR and between e4d3712 and 43a7774.

📒 Files selected for processing (4)
  • hooks/versioned_redirects.py
  • mkdocs.yml
  • overrides/main.html
  • overrides/redirect.html

@dpage dpage force-pushed the susan-pg_semantic_cache branch 3 times, most recently from ba4569e to 8beb111 Compare March 25, 2026 11:23
Add versioned docs for pg_semantic_cache (v0.1.0-beta4 + Development),
with entries in versioned_docsets, nav_categories, welcome page, and
.gitignore. Uses hyphenated URL path (pg-semantic-cache/) to match
multirepo plugin output.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@dpage dpage force-pushed the susan-pg_semantic_cache branch from 8beb111 to f48baa6 Compare March 25, 2026 11:33
@dpage dpage merged commit 0086aca into main Mar 25, 2026
2 of 3 checks passed
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