Thanks! it's probably not the best tool, but it's one I'm familiar with. I love diving into commit histories and reading what developers say in their commits (especially giant corporate private projects where they're so sure no one will ever read them... I read them 👻) and I really wish I could look at, to pick one at random, Tolkien's commit history and see how the work evolved over time. Of course we have his diaries but there's something very specific and personal about seeing a specific change to a line, or a word, that I've seen in code and wish I could see in other written media. That's what I want to capture with my writing. If I ever do publish a book of poetry or short fiction (or a novel, assuming I ever finish one 😓) I imagine I'll cut a release branch for posterity and keep editing them if I so desire, but that decision feels like a long way off.

Long-term, I want to write a tool for collaborative storytelling that incorporates a VCS like git but in a way that's a lot more accessible to writers who aren't also developers. git is a cool tool but it's intimidating for non-devs and with good reason. Part of what I'm doing is figuring out a workflow that works for me, and then maybe I'll build an editor that makes that workflow easier.