Hi Bitbucket team,
Our workspace prasadnpawar is showing the warning "This workspace is getting close to the 1 GB size limit". We found the cause and removed it from history, but the reported size hasn't changed. Could an agent please run garbage collection on the repository below?
Repository: prasadnpawar/veer-matrimony-android
What we did (31 Oct 2026):
- Large
.aab build files had been committed many times in the past (~793 MB in total). - We rewrote the history with
git filter-repo --invert-paths --path app/release (plus two other small files). - We force-pushed all 13 branches (
git push --force --all). All branch heads on Bitbucket now point to the rewritten commits; we checked this with git ls-remote. - The repository has no tags.
- A fresh
git clone --mirror of the repo is 30 MB (git count-objects -vH → size-pack: 30.21 MiB). Before the rewrite it was 824 MB.
What we see: more than 30 minutes later, the repository size in Bitbucket and the workspace warning haven't changed.
Our questions:
- Could you run garbage collection on
prasadnpawar so the unreferenced objects are removed and the size recalculated? - Do open or declined pull requests keep the old commits alive and block the size from dropping? If so, should we decline or delete those pull requests first, and is there anything else we need to do on our side?
- Is there a way for us to trigger the size recalculation ourselves next time?
We're on the Free plan, so we can't open a support ticket directly. Thanks for your he
