A fresh clone is much larger than the current source tree:
- checkout: about 1.1 GB
.git: about 1.0 GB- current files outside
.git: about 50 MB
Most of the Git data appears to come from old generated mobile binaries, including:
flutter/android/jniLibs.zip (about 100 MB per revision)- Android
libcactus*.so files (about 40–45 MB per revision)
cactus.xcframework.zip files (about 15 MB per revision)
Could these generated archives be kept out of Git and published through releases or CI artifacts instead?
Adding ignore rules can prevent the repository from growing again. Reducing the existing clone size would also require a maintainer-coordinated history rewrite, since deleting files in a new commit does not remove their old blobs.
A fresh clone is much larger than the current source tree:
.git: about 1.0 GB.git: about 50 MBMost of the Git data appears to come from old generated mobile binaries, including:
flutter/android/jniLibs.zip(about 100 MB per revision)libcactus*.sofiles (about 40–45 MB per revision)cactus.xcframework.zipfiles (about 15 MB per revision)Could these generated archives be kept out of Git and published through releases or CI artifacts instead?
Adding ignore rules can prevent the repository from growing again. Reducing the existing clone size would also require a maintainer-coordinated history rewrite, since deleting files in a new commit does not remove their old blobs.