Hey People of Github,
I’m still learning the ins and out of using Git in projects. I’m on a student animation project in which we’re going to be making several 3D animated shorts. Often one file will link to another. In order to work non-destructively, we always save incrementally, but this ends up with us having 100+ versions of the same file, and having to relink things everytime a new file is made.
For this project I want a way to still be able to revert to older versions without having to have hundreds of files. Git seems perfect for this application, but getting into the particulars has made me question that a bit, so I was hoping I could get a straight answer here.
- First off it seems Git is build to keep track of versions of the whole project, rather than versions of individual files within that project. Since in our case the project won’t really be versioned in it’s entirety, I’m unsure if it’s fit for my use case.
- I also want to set it up in a way that puts as little strain on the artists as possible. It seems that Git wants to have a human tell it what to do, with very little automation, and I don’t want to interrupt their workflow like that. Especially since they’ll be saving their work hundreds of times per file.
So, Is Git suited for this and have I just not quite understood it yet, or should I save myself the time and look for a different solution?