-
Notifications
You must be signed in to change notification settings - Fork 2k
[DOC] Sync docs #5705
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
[DOC] Sync docs #5705
Conversation
Reviewer ChecklistPlease leverage this checklist to ensure your code review is thorough before approving Testing, Bugs, Errors, Logs, Documentation
System Compatibility
Quality
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Add initial public documentation for Chroma Sync feature This PR is documentation-only and publishes the first set of docs for the new Chroma Sync capability. It adds two new pages (overview and GitHub integration guide), updates sidebar navigation so the pages surface under the Cloud section, and includes new screenshots/graphics. No product code or APIs are changed- Key Changes• New docs: cloud/sync/overview.md explaining what Sync is and how it works Affected Areas• Documentation site content This summary was automatically generated by @propel-code-bot |
docs/docs.trychroma.com/markdoc/content/cloud/sync/github-sync.md
Outdated
Show resolved
Hide resolved
docs/docs.trychroma.com/markdoc/content/cloud/sync/github-sync.md
Outdated
Show resolved
Hide resolved
docs/docs.trychroma.com/markdoc/content/cloud/sync/github-sync.md
Outdated
Show resolved
Hide resolved
cc81ec0 to
1ec06a5
Compare

Description of changes
Summarize the changes made by this PR.
Test plan
How are these changes tested?
pytestfor python,yarn testfor js,cargo testfor rustMigration plan
Are there any migrations, or any forwards/backwards compatibility changes needed in order to make sure this change deploys reliably?
Observability plan
What is the plan to instrument and monitor this change?
Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs section?