Repository size not updating after clean up

[daniel_cheng]

Hi ,

I recently performed a cleanup on one of our repositories, but the repository size displayed in Bitbucket has not updated accordingly.

Below are the commands I executed:

git reflog expire --expire=now --all
git gc --prune=now --aggressive
git push origin --force --all
git push origin --force --tags

When I run "git count-objects -vH" locally, I can see that the repository size has been reduced.

Could you please advise whether there's a delay in size recalculation on Bitbucket's side, or if any additional steps are required on my end?

Thank you.

[Ignacio Ampuero]

Hey!

If you’ve done some cleanup (like history edits, rebases, squashes, or other history modifications) and pushed it, then the remote repo should now be as clean as the local one.

Unfortunately, the reflog and gc commands are local operations and aren’t transferred when pushing to a remote. Bitbucket has its own garbage collection system, which runs periodically or based on repository size.

So, one option is to wait for an Atlassian team member here on the forums to notice the issue and trigger a GC on your repo—or simply wait it out.

This has been a recurring issue on Bitbucket and has been resolved by the Atlassian team in the past.

Hope that clear things up!