docs: clarify metadata-only PATCH does not reindex#784
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| 🔵 In progress View logs |
supermemory-mcp | 215493f | Mar 17 2026, 05:02 PM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
supermemory-app | 6ce7357 | Mar 17 2026, 08:55 PM |
How to use the Graphite Merge QueueAdd 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 finished @MaheshtheDev's task in 1m 56s —— View job Review Complete
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:
Score: 10/10 Clean documentation update with consistent messaging across all affected docs files. |
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
215493f to
6ce7357
Compare

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