Skip to main content

​
How Versioning Works

Every time you commit changes in your workspace, a new version is created. Raycaster Doc uses lakeFS under the hood — a Git-like version control system for data — so every commit is an immutable snapshot you can revisit at any time.

​
What Gets Versioned

  • File uploads and replacements
  • Directory creation and deletion
  • File renames and moves
  • AI-generated edits committed from chat

​
Viewing History

Click the History button on any document to open the version history modal. You’ll see:
FieldDescription
Commit hashShort identifier for the version
CommitterWho made the change
TimestampWhen the commit happened
MessageAI-generated or user-provided commit message
Up to 50 commits are loaded per page, with pagination for longer histories.

​
Pinning a Version

Select any commit from the history modal to pin the viewer to that exact version. When viewing a historical version:
  • The URL updates with a commitId parameter (shareable and bookmarkable)
  • A version banner appears showing commit metadata
  • Edit actions are disabled — the view is read-only
  • The document renders exactly as it existed at that point in time

​
Commit Messages

When committing staged changes, Raycaster Doc can generate a commit message summarizing your changes. You can also write your own. Commit messages help your team understand what changed and why when browsing version history.

​
Atomic Commits

All staged changes are committed together in a single atomic transaction. Either everything succeeds or nothing changes — there’s no partial commit state. This ensures your project history is always consistent.

​
Selective Commits

If you only want to commit some of your staged changes, you can select specific items from the diff view. Unselected changes remain staged for a future commit.