My team's repo size exceed 1.0GB and I was successfully reduced its size to 490.1 MB. However, after I push the cleaned bare repo up, it moved those big blobs on remote to unreachable commit instead of removing them.
After some research, I found BitBucket admin has the ability to run a 'git gc' command on the remote repo to collect and clean those unreachable commits. Is that the only way to do this?
Thanks in advance!
As this guide suggests, you'd need to open a support case with us to force trigger GC. However, in your case it's not that important as 1 GB is a soft limit, i.e. you get a warning but can keep working with the repository just as normal. GC will eventually kick in and remove that large blob.
You didn't mention the repo in question so I took a guess which one you meant and ran GC for it which reduced its size significantly.
If that wasn't the right one, please proceed with opening a support case.
Hi everyone, The Cloud team recently announced 12 new DevOps features that help developers ship better code, faster ! While we’re all excited about the new improvements to Bitbucket ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events