Repository size not reduced after git filter-repo history rewrite — requesting garbage collection

[tksenthil]

On 20 May 2026, I rewrote the history of my repository tksenthil/sites-server using git filter-repo to remove large binary files from old commits, then force-pushed the cleaned history to main.

Five days later, the repository still reports its pre-rewrite size. It currently shows approximately 929 MB, whereas the actual reachable repository size after the cleanup is approximately 310 MB. The orphaned objects from before the rewrite do not appear to have been garbage collected.

The repository has only a single branch (main) with no other branches and no tags, so all pre-rewrite objects are fully unreachable. There are also no open pull requests referencing old commits.

I am the owner of the tksenthil workspace. Could an Atlassian staff member please run garbage collection on this repository so the reclaimed space is reflected?

Current main HEAD: 7c4772c4637b0622c9eeb20ef735d73af4d21a35

Thank you.

[Ben · Accepted solution]

Hi @tksenthil 

I've executed a gc against that repository from the server-end - it reduced it from 934MB > 311MB.

Cheers!

- Ben (Bitbucket Cloud Support)

[Arkadiusz Wroblewski]

Hello @tksenthil 

I requested assistance for you. An Atlassian Support Engineer will review the post and respond in this thread within 2 business days.