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
There still seems to be large blobs. I will remove the SeoulOSMMirror.gpkg which is causing bloat, but I think a number of the other sample data files need to be pruned or at least use a smaller subset of data to keep the repo size relatively lean. Storing PDF files etc in the repo is also less than ideal so we need clear resolutions and better data management practices.
There still seems to be large blobs. I will remove the SeoulOSMMirror.gpkg which is causing bloat, but I think a number of the other sample data files need to be pruned or at least use a smaller subset of data to keep the repo size relatively lean. Storing PDF files etc in the repo is also less than ideal so we need clear resolutions and better data management practices.
To get the blob sizes:
source: https://stackoverflow.com/questions/10622179/how-to-find-identify-large-commits-in-git-history
Results ( Subset>250kb):
The text was updated successfully, but these errors were encountered: