You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This repo is nearly 1000 times larger than it was two years ago. A couple years ago a clone of this repo downloaded perhaps 1-2 MB of data. Now it is up nearly 1GB. This seems to be because of
netCDF files intentionally checked into version control for tests (e.g. 1982a88)
compiled artifacts accidentally checked into version control in prior commits. (a58453f). CI can ensure that this doesn't happen.
This large checkout size makes it difficult to download this code especially in an automated pipeline, and adds friction to working with this code base.
Unfortunately, adding data to git repositories is irreversible without rewriting the history (e.g. using git filter branch). The files remain in the .git folder even if a subsequent commit deletes the files from the working tree.
Would you be open to either
Moving these data to a another location (e.g. a git submodule/FTP etc) and rewriting the history to remove them?, or
using .gitattributes to remove this datafiles from the tarballs built by github, so that users can download the source quickly w/o the test data.
(2) is a lightweight solution that I have found works well with other repos with large test data checked into version control. This is an example of a .gitattributes that removes a directory of test files:
Describe the bug
This repo is nearly 1000 times larger than it was two years ago. A couple years ago a clone of this repo downloaded perhaps 1-2 MB of data. Now it is up nearly 1GB. This seems to be because of
This large checkout size makes it difficult to download this code especially in an automated pipeline, and adds friction to working with this code base.
Unfortunately, adding data to git repositories is irreversible without rewriting the history (e.g. using git filter branch). The files remain in the
.git
folder even if a subsequent commit deletes the files from the working tree.Would you be open to either
(2) is a lightweight solution that I have found works well with other repos with large test data checked into version control. This is an example of a
.gitattributes
that removes a directory of test files:To Reproduce
The text was updated successfully, but these errors were encountered: