Repository size not reduced after large file removal

[jhlchan]

I am on the free plan, so I get an email warning because my repository (jhlchan.bitbucket.io) has size 1.3GB.

I removed a large file in it by git-filter-repo, and my local git count-objects -vH shows 880MB.

After a git push --force, my local git size is still 880MB, but remote repository size is now 2.25GB.

I read through related BitBucket articles, and this looks like somehow both my new and old copies are in my repository. Can the support team do a garbage collection for me?

If this can be resolved, may I ask what is the proper thing I should do to avoid the same thing happening (that is, end up with two copies after git-filter-repo (which rewrites history) and git push --force).

Thank you for your attention and help.

[Brant Schroeder · Accepted solution]

@jhlchan welcome to the Atlassian community 

I have escalated to Atlassian support.

[jhlchan]

Thanks.

[Ben]

Hi @jhlchan 

I've executed a gc against the repository - it has reduced to 880MB.

Cheers!

- Ben (Bitbucket Cloud Support)

[jhlchan]

Many thanks!

Does this (two copies of repository on remote) happens every time when git-filter-repo rewrites history and then I issue git push --force?

[jhlchan]

Thanks for the effort.