Hello.
After removing the file change history of old commits with bfg and garbage collection, the local repository has actually shrunk. However, the workspace storage used space and the size in the
Repository details increased on the contrary.
How to initiate garbage collection on the server?
Regards, Sergey.
Hi Sergey,
I've checked for any workspaces tied to the email address you've used to raise this post and cannot see any workspaces. I've performed an expanded search on your name and can't find any workspaces > 1GB with the same name either.
Can you please raise a new post with the email address tied to your large workspace so we can take a look?
Cheers!
- Ben (Bitbucket Cloud Support)
Good afternoon.
Before making changes to an important workspace, I test the methodology on a test workspace ([REDACTED], repository [REDACTED])
It was on this one that I saw that instead of decreasing in size after the cleanup, the repository only increased in size
I first imprompted the full repository (size-pack: 334.16 MiB) on bitbucket, then I cleaned it up to (size-pack: 146.73 MiB) and push the changes. As a result, the repository grew to 489.82 MB on bitbucket.
Regards, Sergey.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A repository's size is expected to increase temporarily, as performing cleanup operations creates garbage that must be cleaned up from the server side before the size can reduce.
Can you please try again and refrain from deleting the repository so that I can execute this from my end?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.