-
Notifications
You must be signed in to change notification settings - Fork 27
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
Optimize repo size #241
Comments
@danazkari I made a fork and try with ! [remote rejected] refs/pull/94/head -> refs/pull/94/head (deny updating a hidden ref) Maybe we can try |
`➜ eosrate java -jar /Users/rub/Downloads/bfg-1.13.0.jar --strip-blobs-bigger-than 60M eos-rate.git Using repo : /Users/rub/Documents/git/EOSCR/eosrate/eos-rate.git This repo has been processed by The BFG before! Will prune repo before proceeding - to avoid unnecessary cleaning work on unused objects... Scanning packfile for large blobs: 11000 Protected commitsThese are your protected commits, and so their contents will NOT be altered:
CleaningFound 543 commits Updating 69 Refs
Updating references: 100% (69/69) Commit Tree-Dirt History
Deleted files
In total, 357 object ids were changed. Full details are logged here:
BFG run is complete! When ready, run: git reflog expire --expire=now --all && git gc --prune=now --aggressive` eosio.cdt-1.4.0.x86_64.deb | e140d558 (67.3 MB) |
I used, the repo size is fixed
|
Remove large unused git objects to reduce repo size.
The largest file is an idx called something like
.git/objects/pack-f8...
that has a large object of over 70mb thats making cloninfg the repo really slow.we need to remove that object from the history también.
The text was updated successfully, but these errors were encountered: