Skip to content

docs: clarify metadata-only PATCH does not reindex#784

Merged
graphite-app[bot] merged 1 commit intomainfrom
03-17-docs_clarify_metadata-only_patch_does_not_reindex
Mar 17, 2026
Merged

docs: clarify metadata-only PATCH does not reindex#784
graphite-app[bot] merged 1 commit intomainfrom
03-17-docs_clarify_metadata-only_patch_does_not_reindex

Conversation

@MaheshtheDev
Copy link
Member

@MaheshtheDev MaheshtheDev commented Mar 17, 2026

Updates docs to match the new behavior where metadata-only PATCH updates do not trigger reindexing:

  • update-delete-memories/overview.mdx — Distinguishes content changes (reindex) vs metadata-only (no reindex), adds a note about accepted-style updates
  • document-operations.mdx — Clarifies that only content changes trigger reprocessing
  • add-memories.mdx and add-memories/overview.mdx — Add notes on metadata-only behavior
  • memory-api/ingesting.mdx — Splits update behavior into content vs metadata-only
  • memory-api/creation/adding-memories.mdx — Adds note for the “Adding Additional Metadata to Files” flow

@cloudflare-workers-and-pages
Copy link

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
🔵 In progress
View logs
supermemory-mcp 215493f Mar 17 2026, 05:02 PM

@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Mar 17, 2026

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs
supermemory-app 6ce7357 Mar 17 2026, 08:55 PM

Copy link
Member Author


How to use the Graphite Merge Queue

Add the label Main to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@claude
Copy link

claude bot commented Mar 17, 2026

Claude finished @MaheshtheDev's task in 1m 56s —— View job


Review Complete

  • Fetch PR diff and existing review comments
  • Analyze documentation changes for accuracy
  • Check for any code changes that need review
  • Submit review summary

Overview: Documents the existing behavior that metadata-only PATCH updates don't trigger reindexing.

Issues found: None — this looks good to ship.

The PR contains:

  • 6 documentation files clarifying metadata-only vs content update behavior. The updates are consistent and accurately distinguish when reindexing occurs.
  • 1 code file (apps/web/components/document-modal/index.tsx) with only a formatting change (line wrapping + trailing comma on the regex match). No functional change.

Score: 10/10

Clean documentation update with consistent messaging across all affected docs files.

@graphite-app
Copy link

graphite-app bot commented Mar 17, 2026

Merge activity

Updates docs to match the new behavior where metadata-only PATCH updates do not trigger reindexing:

- **update-delete-memories/overview.mdx** — Distinguishes content changes (reindex) vs metadata-only (no reindex), adds a note about `accepted`-style updates
- **document-operations.mdx** — Clarifies that only content changes trigger reprocessing
- **add-memories.mdx** and **add-memories/overview.mdx** — Add notes on metadata-only behavior
- **memory-api/ingesting.mdx** — Splits update behavior into content vs metadata-only
- **memory-api/creation/adding-memories.mdx** — Adds note for the “Adding Additional Metadata to Files” flow
@graphite-app graphite-app bot force-pushed the 03-17-docs_clarify_metadata-only_patch_does_not_reindex branch from 215493f to 6ce7357 Compare March 17, 2026 20:48
@graphite-app graphite-app bot merged commit 6ce7357 into main Mar 17, 2026
8 of 9 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