docs: document table branches in versioning guide#275
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a Branches section to the versioning guide so users know table branches are available across Python, TypeScript, and Rust (including on remote tables served by LanceDB Enterprise).
Changes
tables/versioning.mdxcoveringcreate,list,checkout,delete,current_branch, version-pinned branch checkout, and opening a branch directly from the connection.snippets/tables.mdx.Context
Branch operations were just exposed on remote tables and surfaced through the Python and TypeScript bindings, alongside a new
branch=argument onopen_table()and acurrent_branch()accessor. The docs had no branches coverage previously.