| To jump on the wagon here - at its core git is just compressed snapshots. Having to 'unfuck your branch' is a result of doing more than just storing compressed snapshots. This is probably because all the training material and tutorials assume people want to do more than just snapshots, so as you follow along when getting set up it's easy to get into those kinds of situations. As others have said, doing the compressed snapshot workflow is as easy as adding everything to a git repository, and committing it every time you want to make a snapshot. The biggest hurdle is having each snapshot 'replace' the current one if you want to go back and look at it, but that's not a hard thing to adjust to for the value you get by using git's machinery for the snapshot workflow: - fast and efficient remote backups - greater compression (by using a shared object store for all snapshots) - easy comparison of different snapshots - bisection of snapshots to identify when a bug was introduced (including ability to easily automate running tests while bisecting) - ability to change workflow in the future as needs change, in particular adding in remote collaborators, without having to change versioning system/workflow (well not too much of the workflow) - rich ecosystem to easily publish source if desired at some point - and lots more! Many of these things are possible when you have a list of compressed archives of your source folder, but git really does make it much easier and you don't need to go all in on complex workflows to take advantage of it. |