Expand description
Version-control (“Git for Data”) use cases.
Sits on top of the MVCC snapshot manager and persists commit
metadata in the red_* collections declared in
crate::application::vcs_collections. Mirrors the git command
surface: commit, branch, checkout, merge, cherry-pick, revert,
reset, log, diff, status, tag.
Designed to mirror the Graph/Query use-case pattern: thin struct
parameterised over a RuntimeVcsPort trait implemented by
RedDBRuntime. No storage logic lives here — only validation and
delegation.
Structs§
- Author
- Checkout
Input - Commit
- Conflict
- Create
Branch Input - Create
Commit Input - Create
TagInput - Diff
- Diff
Entry - A single entity-level change between two commits.
- Diff
Input - LogInput
- LogRange
- Merge
Input - Merge
Opts - Merge
Outcome - Result of a merge operation. Non-empty
conflictsmeans the merge is paused — user must resolve shadow docs inred_conflictsbefore committing. - Ref
- Reset
Input - Status
- Status
Input - VcsUse
Cases
Enums§
Type Aliases§
- Commit
Hash - A commit hash. 64-char lowercase hex (SHA-256 truncated or full).
- RefName
- A full ref name like
refs/heads/mainorrefs/tags/v1.0.