I am getting the following warning when I push to my workspace (wildidea):
```
remote: WARNING This workspace is getting close to the 1 GB size limit
remote: If this workspace reaches the 1 GB size limit, you will not be able to push
remote: or merge new commits to any repositories in this workspace.
```
I ran git-filter-repo multiple repos and force-pushed, achieving significant size reductions. However Bitbucket is still reporting that I am close to my limit.
The instructions in the reduce-repository-size article suggest that Bitbucket may need to run GC manually. None of my repos are close to the single-repo size limit, so they aren't going to trigger automatic GC that way. My understanding of the docs is that it will need to be run by Atlassian Support, and the docs suggest opening a support ticket.
Can you run GC on these repositories please:
We have done this once before, but it's built up again. I will probably move some of my projects to another workspace the next time this happens.
Hi @hiebj
I've just executed server-side garbage collections against those repositories, this has reduced the size by approximately ~288MB.
Cheers!
- Ben (Bitbucket Cloud Support)
Hi,
Bitbucket usually handles GC automatically in the background.
If the repository size is still large even after cleanup, you may need Atlassian support to run a manual GC on the remote repository.
You can also verify the local repo size using git count-objects -vH before raising the request.
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.