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
Is your feature request related to a problem? Please describe.
I noticed today when cloning the stactools repo it was getting sizable. It's 32MB, of which 8MB is the main branch (large files are in the test directory)
Describe the solution you'd like
Prune out old large files from the git history, I suspect at least some of these files are old test files
Describe alternatives you've considered
Live with it, which is fine - this is not critical, you can always do shallow clones. However I think that with the codebase largely stabilized now the old files can be pruned from the tree safely and will result in a leaner repo when cloning
The text was updated successfully, but these errors were encountered:
I'm a little wary of modifying public git history. 32MB doesn't seem that big to me in the grand scheme of things for a geospatial repo, and since we are maturing, most users will be pip-installing from a tagged release anyways?
If we were going to, it looks like this culprit is obvious (I used this):
Is your feature request related to a problem? Please describe.
I noticed today when cloning the stactools repo it was getting sizable. It's 32MB, of which 8MB is the main branch (large files are in the test directory)
Describe the solution you'd like
Prune out old large files from the git history, I suspect at least some of these files are old test files
Describe alternatives you've considered
Live with it, which is fine - this is not critical, you can always do shallow clones. However I think that with the codebase largely stabilized now the old files can be pruned from the tree safely and will result in a leaner repo when cloning
The text was updated successfully, but these errors were encountered: