If you want to track a folder, then you run. This will save a lot of space in your GitHub repository. If you do collaborate with others, you will also need to manage their access to that other shared repo. iso extension to LFS repo and when you push the files, a pointer to file will be stored in GitHub repo, instead of the actual file. GitHub won't be able to see it (the URL of that submodule will not resolve to a public address that GitHub can read) but from your own machine you will have access to both. GIT LFS STORAGE LIMITS: Git lfs is free to use, but that freedom comes with a limit. Git is not good at dealing with binary files in general since it can't generate good delta: binary files, especially when compressed, tend to change a lot between versions, while text files usually change only partially and locally.Īnother solution would be to host a git repository locally (or on a shared drive) only for the assets and have it be a submodule in the main repository. What is the limit on Github Large File Storage (LFS). In that drive, you will have to do the versioning manually. I would only keep code and small assets that are unlikely to change in git itself and have all other files on a shared drive (and add a README files in folder where they are expected to copied into when building the whole game), especially the source files for textures and models/animations that tend to be big.
