nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Free workspace read-only after history rewrite — manual GC request

Joe DiVecchio_o4hurc

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

Accepted answers

Syahrul

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

All comments

Tomislav Tobijas

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

Joe DiVecchio_o4hurc

Thank you!

Syahrul

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud