Garbage Collection Request?

[Dev DS]

Hello,

I recently used a filter branch locally to remove commits containing large binary files in my staff-travel repository. Because I wanted to ensure that I didn't wreck the repo, I renamed it in Bitbucket to staff-travel-original and created a new repo called staff-travel and pushed the filtered updates to that (which is showing as 3.1 MB in size). Once I'd checked everything was okay, I deleted the staff-travel-original repo which was around 977 MB in size, however it hasn't reduced the workspace storage size.

Any assistance would be appreciated, thanks.

[Theodora Boudale]

Hi @Dev DS and welcome to the community!

After deletion of your large repositories, please allow up to 30 days for the background cleanup job to run and total workspace size to be re-adjusted. The garbage collection may reduce the size of the non-deleted repos; however, since you pushed the filtered updates to a new repo and not to the original one, and the original ones was deleted, a garbage collection won't help in this case.

Please note, that the size enforcement will take place on April 28, 2025, until that date your workspace is not going to be impacted by the new limits. The new size will be reflected within 30 days of repository deletion.

Our team is working on improving the cleanup time and it is planned to be implemented prior to limits enforcement changes taking place.

Kind regards,
Theodora