Hi @steve-fentrack
It's actually expected for a repo to increase in size after performing maintenance operations, as it creates garbage that needs to be cleaned from our side with a server-side garbage collection.
I executed a gc and this reduced the size from 629MB to 203MB.
You had a much larger repo at 2.9GB that I've also executed a gc against - this reduced down to 1.1GB.
Overall - your workspace is still using over 3GB - if your aim is to reduce the size < 1GB I'd suggest finding any large binary files using the below command and following documentation to remove/convert these files to GIT LFS:
git rev-list --objects --all \
| git cat-file --batch-check='%(objecttype) %(objectname) %(objectsize) %(rest)' \
| awk '/^blob/ {print substr($0,6)}' \
| sort -r --numeric-sort --key=2 \
| numfmt --field=2 --to=iec-i --suffix=B --padding=7 --round=nearest
Once you've done so, please let me know and I'll perform subsequent gc's (just give me the repo filesize rather than sharing the name as this is a public forum).
Alternatively, you can upgrade to our Standard/Premium plans which offer unlimited workspace size:
Cheers!
- Ben (Bitbucket Cloud Support)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.