Repository Size is different after clone to new repository

Question

We have issue with our repo, We have old repo which is 803.8 MB, but in localhost, it is around 240 MB.

After we clone the old repo, to the new repo the size in bitbucket cloud is 240 MB. It is same with our localhost size.

Why our old repo is much bigger than it should be? Do you need to run GC to reduce the size of our repo, or we can run the GC by our self?

Syahrul · Answer

Hey @manyang

We've setup automated GC to run whenever necessary, but if you find you need an immediate GC after a cleanup, please feel free to create a community post. We're here to help you manually run the GC.

Regards,
Syahrul

manyang · Answer

Thank you @Syahrul for your help, so do i have to do this process again, or once you activate it, it is active until later?

Syahrul · Answer

Hi @manyang

Welcome to the community!

Because of how git operates, repositories can accumulate dangling/unreachable commits and blobs over time, which can lead to a bigger storage footprint. To keep things tidy, a GC  is needed now and then, and I've already taken care of that for you.

So good news—your total workspace storage is now below the 1 GB limit!

Regards,
Syahrul