Closed samusz closed 2 years ago
Thanks for pointing this out and I see that as well. What I don't know is how to safely fix it.
Maybe git rebase --autosquash master
?
The bloating is due to a bunch of (pretty) old .ipynb files which I used in version 1. Why specifically 8 or 9 versions of one notebook and one or 2 other notebooks are still present is unclear to me.
I've tried in many ways to remove these files and/or shorten the history to e.g. only contain v4+ related files, but to no avail.
Not sure what other options are available. At least one suggestion I came across is deleting the Github repo, create a new repo with the same name and commit the contents of the current master.
I am not git nor gihub expert so can't really give safe advices. If I understand well what I've read, git squash, deleting branches or rebase could be a solution.
HTH
Thanks for your suggestions!
It might be difficult to go the route of rewriting history as Mosè pointed out. But nevertheless I'm glad you raised the issue! I pretty much have the package all the time in my dev directory so I hardly ever download it.
Anyway, what I think I'm going to do is to move the contents of StatisticalRethinking.jl to a new directory probably called StatisticalRethinkingBase.jl (or SRBase.jl) and use the current version more as a general intro to the StatisticalRethinking GitHub organization.
After asking for some feedback on Julia discourse I'll implement the above solution.
The large size issue only occurs if you dev
the package, it does not happen if you add
the package.
As soon as StatisticalRethinkingBase.jl is published I'll let you know and close this issue.
Thanks again for your help!
Hi @samusz ,
Given that I now have a better understanding of the (somewhat limited, only on initial dev
-ing) impact of this issue I might hold off a little longer with creating StatisticalRethinkingBase.jl. Such a change will have consequences for many of the notebooks in the Turing and Stan Julia projects that use StatisticalRethinking.jl. But if it really becomes/remains a major issue for you or others, please ping (@goedman) me. For that reason (and in case others run into it), we should probably leave this issue open.
My branch is up to date '
So for about 4 Mo of data the .git is 1 Go Some branches needs squashing ?