hologit

To project Git branches declaratively, define a .holo/ workspace with TOML configs for holosources and holobranches, then run git holo project to compose mapped sources and compute the resulting output tree hash.

A declarative virtual holobranch is a computed Git tree that combines content from multiple mapped sources and applies transformations. It removes manual assembly by using layered inclusion rules and topological ordering to build deterministic output trees.

Containerized lenses transform projected Git trees by executing Docker-based transformations in internal and external phases. You define these lenses in TOML configs to deterministically modify the projected content during the git holo project workflow.

Yes, cached builds avoid redoing transformations by caching lens results using deterministic spec hashes. When projecting Git branches across multiple repositories, the system checks these hashes to skip unchanged work and compute output trees efficiently.

Generating Kubernetes manifests and documentation from Git requires a .holo/ workspace setup. You must define TOML configurations for holobranches, holosources, holomappings, and hololenses to establish the deterministic rules before executing the projection.

The best way to mix multiple repositories and generate artifacts deterministically is using declarative holobranches with Git object primitives. This approach applies topological ordering and containerized lenses to ensure consistent, cached output trees without manual assembly.