Large repo size

Viktor Minkovski

Hi all, 

One of our repos got too big 2.3 GB. The issue is the usual one with big files in the history. 

After several attempts to use the proposed tool Bfg, the size is now up to 3.8 GB and nearing the limit. 

On the other hand, when cloned locally, the size of the remote repo is 1.3, which while still big, is at least acceptable. 

Can someone share some hints on how is the difference between remove and local clone possible? Is there anything else I need to do? The usual git gc does not seem to help.

Thanks in advance for the support.

Theodora Boudale

Hi Viktor!

If you rewrite history and push it to Bitbucket, the repo's size will go up because the repo will contain both new commits and old ones (before the history rewrite). A garbage collection is needed on the Bitbucket Cloud repo to remove the old references and for the repo's size to get reduced. This runs on every push but with different arguments depending on several different conditions, so the dangling commits may not get removed immediately.

I can run a git gc for your repo that should remove these dangling commits. Can you let me know the first two letters of the repo name (or any other combination of letters that will help me identify it)? I checked the repos your account has access to and I do not see one with a size of 3.8 GB.

Kind regards,
Theodora