historical drafts: sketch potential cli of hitch.
historical drafts: sketch potential cli of hitch.

... a few days ago when "bond" was one of the leading name candidates for this component.

Highlights: idea of iteratively altering the working tree on disk, and emitting snapshots (like git commits) after a set of operations.

While we're reviewing this: another idea in parallel to this model: you might wish to make stack of workspaces (... a concept not yet referenced in any of these drafts, sorry!  tl;dr: an ordered list of hitch database, which, like a unionfs, you can just look through to get the first answer.) in which the top element of the stack is simply your "nightlies": this would allow you to look "forward" in your build pipelines, make sure everything downstream works... and then you can make "real" releases by importing things from your "nightlies" tree, getting the best of both worlds of look-forward testing and releasing only when confident.  (The linter functions to make sure your operations maintain full connected, walkable history would be essential to avoiding human error here, ofc.)

Signed-off-by: Eric Myhre <2346ad27d7568ba9896f1b7da6b5991251debdf2@exultant.us>

polydawn/hitch,polydawn/hitch