I am getting the following output when pushing to my workspace (wildidea):
```
Enumerating objects: 17, done.
Counting objects: 100% (17/17), done.
Delta compression using up to 12 threads
Compressing objects: 100% (10/10), done.
Writing objects: 100% (10/10), 1.72 KiB | 352.00 KiB/s, done.
Total 10 (delta 7), reused 0 (delta 0), pack-reused 0 (from 0)
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.
remote:
remote: Upgrade to a Standard or Premium plan: https://support.atlassian.com/bitbucket-cloud/docs/manage-your-plan-and-billing/#Change-your-plan
remote: Or learn how to reduce your repository size: https://support.atlassian.com/bitbucket-cloud/docs/reduce-repository-size/#Rewind-history-to-undo-large-commits.
```
I ran git-filter-repo on my 3 largest repos (wildidea/rescueally-app, wildidea/rescueally-website, and wildidea/wild-components) and force-pushed, achieving significant size reductions (totaling at least 300 MB). 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 (or every repo in the wildidea workspace?)