A couple of years ago, I was modding a fresh install of Skyrim and thought, "I can use git branches to make it easy to switch between different mod combinations rather than uninstalling/reinstalling mods when something breaks or when I want to change things up." Worked well!
I had branches that were mostly vanilla with enhancements, and then branches that had all kinds of ridiculous mods. If I wanted to switch to playing a ridiculous build of Skyrim, I'd just close the game, checkout the branch I wanted, and start the game.
It's been a couple of years, but I don't recall it being particularly slow switching between branches. I had a pretty beefy rig to begin with, which probably helped.
Fun story, in 2012 I got the idea of making a git based "cloud" save system with branching, to explore multiple story paths in games.
I implemented the FileSystemWatcher (the equivalent to Linux's inotify) component in C# on Windows, was able to detect when games were saved, and commit that to git, and stopped there.
Feel free to implement that, I'd love to save on implementation time 😇
I wish all rules, Ts&Cs, contracts, etc came like this. It might make it less unfeasible to follow what's changed when something forces you to agree to the new version of the terms.
I wanted to automate the setup of my desktop environment, but didn't know what got changed in the individual config files when I tweaked a setting in the UI.
So, I did a git init in ~/.config/, added all files to an initial commit, and then made the change in the UI. Afterwards, a git diff showed the exact changes I wanted.
I used it once for version controlling my master's when I was writing it. I wrote it in Markdown with Pandoc syntax, so it worked. I eventually gave up and just used LibreOffice, though, since it was a hassle
I worked with LaTeX a lot, but none of my collaborators used git. They just dump the files in dropbox. Still nice to use git just for yourself so you can view changes easily.
Both lol. The reason is that I had to render it to DOCX each time for my PI to review it, because she was an old retrograde woman. Therefore, rendering the document, committing changes and reading Git and Pandoc documentation took time -- the time that I could've used to write the actual thing
I've put ASTs directly into git repositories by encoding each leaf as a blob and each tree as a tree. Since git objects are content-addressed, this gives deduplication of ASTs for free, including CSE for sufficiently-pure ASTs.
ifc is an iso standard for 3d construction projects, which includes all aspects of a building data. because ifc is in human-readable form, versions of the same project can be diffed, hence ifc git.
I tried to take hourly snapshots of an already-large Minecraft world using Git, but after a few years of snapshots, the repository became corrupted.
One of the issues was that regardless of any player-based changes that occurred, the spawn regions were always different as they were always loaded in memory.
Not very clever or rare, but extremely useful. On my persistent Unix/Linux boxes, I "git branch /etc" as soon as it comes up. Then all of my admin config gets committed whenever it's changed.