Hello,
My Bitbucket Cloud workspace is on the Free plan, and every push now warns that it is getting close to the 1 GB limit.
Six of its repositories were never rewritten or force-pushed. I measured each one with a fresh git clone --mirror and git count-objects -vH, as the Atlassian team recommends here, and the mirrors are far smaller than the sizes Bitbucket reports. The data arrived in many small pushes and has never been repacked on the server:
Repository (first letters) | Reported by Bitbucket | Fresh mirror clone
ba… | 377.7 MB | 16.2 MB
le… | 69.8 MB | 13.2 MB
ki… | 44.9 MB | 21.7 MB
sm… | 28.3 MB | 20.9 MB
cli… | 13.0 MB | 9.5 MB
ad… | 3.1 MB | 1.0 MB
In four more repositories I rewrote the history today, to remove screenshots that had been committed by mistake, and force-pushed the result. The old commits are now unreachable, but the sizes Bitbucket reports are still far above what a fresh mirror clone holds:
Repository (first letters) | Reported by Bitbucket | Fresh mirror clone
tr.. (four letters) | 132.2 MB | 39.3 MB
fo..-admin-panel | 91.6 MB | 5.5 MB
fo..-client-app | 14.6 MB | 6.8 MB
fo..-backend | 24.0 MB | 3.6 MB
Could a member of the Atlassian team please run a server-side git gc on these ten repositories, so that the unreachable objects are removed and the sizes recalculated?
The workspace ID starts with "gr" and ends with "os". There are no pull requests in these repositories. I can send the exact repository names privately.
Thank you!
