Skip to main content

Module alias

Module alias 

Source
Expand description

Proven Git-object aliases and byte-exact manifest path identities.

Git object IDs hash a blob <len>\0 header as well as file bytes, while content-addressed artifacts use BLAKE3 of the file bytes. This module keeps that distinction explicit: aliases are accepted only after recomputing the Git blob ID from the exact bytes.

Structs§

AliasStore
SQLite storage for proven (git_oid -> blake3(bytes)) aliases.
ExcludedPathClasses
Excluded path totals printed with a zero-read checkout report.
GitOid
A SHA-1 Git object ID represented as its 20 raw bytes, not text.
Manifest
A single view manifest with a fixed path identity encoding version.
ManifestRecord
One byte-exact manifest path and its tagged entry.
ManifestSqliteStore
SQLite representation for raw manifest paths. rel_path is deliberately a BLOB column so SQLite never applies text collation or Unicode normalization.
PlaneKeys
A manifest’s two optional plane keys for a regular path.
TrackedPath
A Git-tracked path with the metadata used to decide whether it can be aliased.
ZeroReadCheckoutReport
The numerator, denominator, and every excluded path class for zero-read checkout reporting.

Enums§

AliasError
Errors raised while proving aliases or preserving path identity.
AliasSkip
Why a candidate was deliberately not entered into the alias table.
AliasWrite
The immutable result of attempting to seed one alias.
GitMode
Git tree modes that determine whether a path can be aliased.
ManifestEntry
The tagged manifest entry schema. Paths live beside entries as raw BLOBs.

Constants§

PATH_IDENTITY_VERSION
The manifest format that stores paths as exact, slash-separated bytes.

Functions§

git_blob_oid
Computes Git’s SHA-1 blob object ID from exact file bytes.
head_tree_entries
Lists HEAD paths from Git metadata without opening working-tree files.
is_lfs_pointer
Returns whether bytes are an LFS pointer. This conservative secondary check protects aliases even if a caller failed to propagate filter=lfs.