Request garbage collection for Bitbucket Cloud

[JohnMapley]

I'm a free user of Bitbucket Cloud, and I had the email saying that my workspace was over 1GB and would go into read only mode if I don't do something about it.

I've shrank the biggest repository in my workspace by using git-filter-repo to remove large files from my repo history, which successfully shrank the repository locally. I have followed their instructions to push it back to bitbucket cloud, but the size reported in bitbucket cloud hasn't changed, so I'd like to request that you initiate a manual garbage collection on it.

[Tansu Akdeniz · Accepted solution]

Hi @JohnMapley 

Welcome to the community.

The Atlassian support team has been notified and they will reach out to you.

[Ben]

Hi @JohnMapley 

I've executed a git gc on the server-side but it's only reduced the size to ~980mb.

The reason for this is that, as part of changes to improve the speed of PR diff, we store binary files in PRs.

• As you have over 2,000 PRs in your repository, the large binary files you've stored have inflated the overall repository size due to these PRs.
• As PR's are purely server-side, this explains why the local size is different vs remote

To resolve this:

• You'll need to duplicate the repository (which will only contain the raw repository data/commits, not the PR's): https://support.atlassian.com/bitbucket-cloud/kb/how-to-duplicate-a-bitbucket-cloud-repository/
• Once the repository has been duplicated - delete the original repository: https://support.atlassian.com/bitbucket-cloud/docs/delete-a-repository/

By performing the above, you'll reduce the overall size of your workspace to within the 1GB limit.

Cheers!

- Ben (Bitbucket Cloud Support)

[JohnMapley]

As suggested I duplicated the repository by mirror cloning it, cleaning it with git-filter-repo, garbage collecting it and then mirror pushing it back to the workspace. Then I deleted the original repo, and that has resolved the problem.

The only thing to be aware of with that approach is that the pull request history is lost, which wasn't a problem in my case.