Repo size discussion (Presently 797.52 MB)

[rwaldron]

Before I spend a significant amount of time deep diving through the repository, is there anything known reason or possible explanation for the present size of the repository? If so, are there any cursory thoughts on how to address?

[SaraJo]

Repo is 19M on my machine currently. Are you looking at a past commit?

[SaraJo]

Scott just pointed out that the .git folder is huge, looking into it.

[gortok]

The issue appears to be there are binary files in the repo (JWBLoader.exe and JWBLoader_osx), I don't know how much it would help; but we could remove those from the repo and include a separate zipped download of these things, and keep the arduino-library for the source itself?

We could also do:

git update-index --assume-unchanged JWBLoader.exe

and the same for the OSX; I don't know if that'd shrink down past versions of the repo (doubt it), but it'd keep it from compounding.

We could also remove the EXE from the revision history using:

git rm --cached JWBLoader.exe

So steps:

• pull down the JWBLoader / OSX Executables.
• Run the git rm -- cached command for those files
• commit/push
• put back in EXE/OSX (if you want them in this repo)
• and do the assume unchanged command I listed above.

But ultimately it comes down to whether you believe the binary files should be in this repo; they should probably be in a standard download somewhere, not in source; but it's up to you.

[gortok]

Looking through the history; it seems like along the way various .zip files were added / various binaries were added and removed; we could always reset the repo to now (losing initial history); and making sure the binary files stay out, and that should solve the issue. Depends on how much the history before now means (I don't see a whole lot to keep; but I didn't work on this for the most part).

[SaraJo]

I don't think it's bad to lose history, will prune the .git folder.

[gortok]

Cool. As long as we keep the binary files in there, it'll just blow up again. Not sure how to handle that other than stick the binaries on S3 and link to them on the Jewelbots Website.