I see your point. In that case, you're probably better off without it. The way I use it, I have a main branch for official ren'py versions and branches from each version for different games with their own commits according to release, then I can experiment upon while being able to rollback to the original version... It does get troublesome depending on what kind of modifications I make, but that is rarely an issue since I can rebase or cherry-pick important parts while managing to keep each commit independent from the others, it's been working so far... And it's a godsend for disk space, since I've been trying lots of different games that clutter with temp files and duplicates and only using file compression doesn't really help. Plus, integrity and diff checks in one tool is quite handy... It does have a steep learning curve, but nowadays I can't really imagine myself without it...GIT is a pain in the ass and creates far more problems than solutions for a single user development project. I have my own version management that works better and is far easier to handle.
I have tried GIT for about two weeks with my project, almost smashed my keyboard about 10 times...
It makes sense for multi developer environments, we're using it at work too, but for my home project, it's just not the right tool.
And...
You will have issues with redoing changes when you did it the 10th time and when the files have changed in a way, that your version management tools can do shit. I reorganize stuff all the time and move whole areas, functions or classes to other (or new) files from one version to another.
I'd love to go into further detail, but I don't think it's the correct thread. Just thought I'd mention it here and see if it generates interest, then maybe I can write a tutorial or something to help other users.