2 ms·
If you're concerned about bloating your Git repository with non-unique binary files (as you should be) a trick I've used in the past that worked really well was
by simonw 3y ago
If you're concerned about bloating your Git repository with non-unique binary files (as you should be) a trick I've used in the past that worked really well was to have a separate project-dependencies Git repository that all of my dependencies lived in.
I was working with Python, so this was effectively a Git-backed cache of the various .tar.gz and .whl files that my project depended on.
This worked, and it gave me reassurance that I'd still be able to build my project if I couldn't download packages from PyPI... but to be honest these days I don't bother, because PyPI has proven itself robust enough that it doesn't feel worth the extra effort.
I keep meaning to set myself up a simple S3 bucket somewhere with my PyPI dependencies mirrored there, just in case I ever need to deploy a fix in a hurry while PyPI is having an outage.