-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Very large git size #115
Comments
You could use the command |
Thanks for the idea @onekiloparsec! I tried with many other things and I could not really get rid of the large files. I'd need to give it another try! Thanks again |
One of the strength of git is ensure data consistency throughout history. Logically, it is very hard to "remove" anything from its data. Again, I'd be happy to help further if you explain a bit more why you think this repo is big. :-) (Not necessarily a reference, but I've worked with 10GB+ repos. It's a pain with the first clone, but after that, it's fine). |
Sure! Sometimes prose has to be cloned and tested in very remote places (like Antarctica) with very limited bandwidth. Also the big files were mostly part of erroneous commits, mostly mistakes. |
Wow, interesting. Indeed, Antarctica isn't probably high-speed connexion. I just stumbled upon this, highly starred: https://github.com/rtyley/bfg-repo-cleaner Looks quite easy to use. |
When cloning prose, the repository weights 83Mb, but the actual code base is only ~10Mb (including notebooks stored in docs). I know this is coming from old voluminous files versioned that I would be happy to remove from git history (we are talking about versions < 1.0).
The text was updated successfully, but these errors were encountered: