Closed dutterbutter closed 2 years ago
when we run git clone <webb-repo>
on essentially any repo that interacts with fixtures, it takes forever to download and git stores a TON of disk space. How should we manage the fixtures and their relation to our different repositories?
Even after removing the submodule entirely and pushing to the remote, a subsequent git clone
is still incredibly bloated.
- Wow! Looks like a lot of git blobs for things related to earlier handling of fixtures in the repo.
protocol-solidity
before any submodules init. This shows the issue is with the git history of the project: ~356MB
I attempted these things on a fork of the protocol-solidity repository.
Using the bfg-repo-cleaner tool to clean the history of blob sizes >1MB:
[BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/)
protocol-solidity
.
~8.7MB
git submodule update --init
:
324MB
482MB
ptau
folder.https://github.com/newren/git-filter-repo
git filter-repo --analyze
Overview
The fixture are getting crazy large in size, every time we do a blob change, it result in like 99% file change from the old ones, so git history ends up storing both files, even though we will use the most recent one.
Downloading all these files is just more waste of time and bandwidth, the repo size will go over half a gigabyte if we continue that way very soon (right now it is around 300mb+).
Potential Solution
Tasks