-
Notifications
You must be signed in to change notification settings - Fork 12
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
Clean up large .faiss files from .git #39
Comments
It looks like we can't do this in a repository that contains pull requests. We can do it by creating a new repo, moving stuff, deleting this one, then renaming it, but I don't know that it's the best idea to engage in that right now. Unfortunately, that doesn't help you, since pip install doesn't have a --depth option and apparently won't anytime soon. I'm leaving this open in case we get the gumption to fix it or have a bright idea. Meanwhile, what I'm seeing is a lot of this:
https://stackoverflow.com/questions/34265266/remote-rejected-errors-after-mirroring-a-git-repository |
Huh, interesting. Yeah like I said it isn't a tremendous issue, I just did it because I had to fork the medifor API anyways (because...reasons, frankly inadequate ones) so I figured I'd give it a shot and report my findings to you folks. |
I noticed there were some large files accidentally committed to the repo. This is more of an inconvenience than a major issue, but it means there's a large pull every time you
pip install
from the git repo (implicit clone). Not sure if you are still actively maintaining this, but if you are interested in purging these files, I was able to shrink the directory from ~160MB to 1.8MB with this protocol. Definitely practice with a backup repo and alternate remote! You can check out my results here.Then comes the fun part. Use dockerized BFG repo cleaner to purge the history:
that will strip the files but it doesn't fully prune them just yet, so then you run
to prune and collect garbage, and voila! .git should be much smaller.
The text was updated successfully, but these errors were encountered: