I am the administrator of a Free Bitbucket Cloud workspace that is currently read-only.
The workspace ID ends in io, and the repository name ends in ot. Bitbucket reports the repository as 1.03 GB.
I removed historical generated .pck and .wasm files using git-filter-repo and successfully force-pushed the cleaned branches and tags. Locally, git count-objects -vH reports size-pack: 124.23 MiB, and git fsck passes.
The “Delete dangling commits when over size limit” Labs feature is unavailable on my account.
Please run manual server-side garbage collection on the repository. I consent to this repository-maintenance GC operation
Hi @Joe DiVecchio ,
I've pinged the forum support team, so someone should get back to you on this within 1-2 business days (or maybe even sooner 🙂)
Cheers,
Tobi
Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Joe DiVecchio
Welcome to the community.
I have triggered Git GC on the affected repository. The size appears to have been reduced. Please review it to confirm this is the expected size.
Let me know how it goes.
Regards,
Syahrul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.