Method
Lore reads a repository’s Git history and plays it back as a map of files. Every caption links the commits it comes from.
reading the map
- pointA file, from its first commit to its deletion.
- neighborsFiles that share a directory or change together. Nearness is not a dependency.
- flashA commit touching a file.
- chapterA stretch of history where the work changed shape, with the commits behind it.
- authorThe name Git records for a commit. It is not proof of who wrote it.
One history to follow
Lore follows the first-parent chain of the default branch, so changes appear as they enter the main line. Work on other branches shows up as the merge that brought it in. An exact rename keeps a file’s identity. A move that also edits the file can appear as a deletion and a creation.
The map has a budget
A large history can hold more files and commits than a browser can draw. Lore then lays out a selection of files and samples the commits it uses to place them. File lifetimes and the timeline still count every commit, and each film reports what it covers and whether it was sampled.