My main question after looking it over though is: given an existing codebase, how could I go about building a decision graph to essentially get "caught up" to current (I guess based on commit history?) to then move forward actively using Deciduous from here on out?
It wouldn’t be hard to make a skill that went through and did this at a basic level if you have a good healthy and well organized git history (most people don’t)
There is already tooling to link commits to nodes and re author chains so you could tell it to explore and start making this.
I might do an experiment trying this with an existing project in the OSS ecosystem tonight, sounds fun
rhgraysonii•1mo ago
http://notactuallytreyanastasio.github.io/deciduous/story.ht...
There is also a living graph of the entire development lifecycle thus far here
http://notactuallytreyanastasio.github.io/deciduous/demo/
I began the project 12 days ago, so this is all very fresh. I extracted it from another tool I built after building it to help me build that tool.