trail
A version-control authoring model built around typed stacks of changes.
trail is a version-control authoring model built around stacks of related
changes. It treats a segment of commit history, rather than an individual
commit, as the unit being formed and amended.
The unit of change
A trail is a segment of commit history: a stack of changes that belongs together. Work can be added to the trail or used to amend it without treating each intermediate commit as a finished unit.
Typed history
Each trail must match a configurable pattern. The pattern gives the trail a type and describes the structure expected of that kind of change.
History boundaries
The model divides history into three regions: an immutable trunk, a malleable middle where trails can be revised, and an open tip where new commits can be captured before they are formed into a trail.
Status
I am currently developing the model and its workflow.