Open jamesmbaazam opened 3 months ago
Thanks @jamesmbaazam! I'll try to have a look now to see which are the large objects in the package. Let me know if you already know this.
This thread may be useful https://github.com/epiforecasts/EpiNow2/issues/538
Right yes, I was getting confused because I was just looking for large files and wasn't sure what it would be (most of the largest ones below in my local version aren't commited):
So the point is that the Git version contains all the histories too, which is ending up being large. Thanks for link @sbfnk, will read and try to implement.
Edit: after a skim it seems like doing this is relatively intricate. As there are not many people using the package currently, I wonder if doing this could be best timed to coincide with a 0.1.0
release. Otherwise, I think it may be that it would need to be done again at that point anyway (likely development will continue to add file histories). Let me know if people disagree about this and think it's a priority to do sooner.
This thread may be useful epiforecasts/EpiNow2#538
Thanks, Seb. I was coming here to post this.
(likely development will continue to add file histories).
It shouldn't add large files. We do want to close out hanging PRs before we do this (and in general).
Thanks for the input all. This is a legacy of pulling the package out of the analysis repo I think
I just tried to clone this repository and noticed it is extremely large (1.78 GiB). Could you consider reducing the size?