Repository size exceeds limit

АЯКС Digital

Hello!

Bitbucket mentions that the size of the repo is currently 4.78 GB of 4 GB. When cloned, the repository weighs less:

count: 0
size: 0 bytes
in-pack: 38024
packs: 1
size-pack: 1.14 GiB
prune-packable: 0
garbage: 0
size-garbage: 0 bytes

Can you please run git gc for the remote repository?

Theodora Boudale

Hi @АЯКС Digital,

I ran a git gc for the repo, and its size has been reduced.

Please keep in mind that if you do a simple clone of the repo in order to run git count-objects -Hv, only the repo's main branch will get cloned. If you want to compare the local vs remote size, I would recommend cloning with git clone --mirror <repo_url>, so that you get all the branches locally, and then run git count-objects -Hv in that mirror clone.

You created a question about this issue on Friday as well, are there frequent force pushes, rebase, or history rewriting in the repo? Frequent history rewrites / force pushes, operations that mark commits as unreferenced / delete commits, will become garbage and thus increase repository size.

You should be able to push to the repo now, however, I would recommend reducing its size further, if possible. You can check this post of mine in a different question with more details:

https://community.atlassian.com/t5/Bitbucket-questions/Revert-bitbucket-repository-state-to-one-day-prior/qaq-p/1908360#M76762

If you decide to proceed with the steps mentioned in that post and rewrite history in the repo with BFG, please keep in mind that the repo's size will get increased again once you push your changes. The repo will then need another git gc for the old commits (prior to history rewrite) to get removed and to get its size reduced. You can let me know here, and I can run another git gc for the repo.

Kind regards,
Theodora