Git Restructuring/Branches for Reduced Clone/Fork Size #28
Description
Git is not the optimal version control system for hardware projects, as I understand it. Cloning or forking the repo incurs the burden of downloading all history, which when looking at STL files that are a handful of MB each, and dozens of STL files, each with several versions, and it blows up to hundreds of MB. Maybe I'm forgetting that Git does a form of compression? Anyhow, there are probably ways to reduce the burden by branching, or otherwise optimizing the history, if not deleting it somehow. As the project is polished and improved, old versions can only really serve as historical markers, but are dead weight otherwise.