Hi @FerFrassia, thanks for reaching out!
I've run git gc in your remote repository and the size has decreased to 792.1 MB. It's normal that this happens from time to time, Bitbucket has automated gc that happen in the background for this reason.
When you push changes to your repository, any objects that become orphan are not immediately deleted. Let's say you amended a commit by changing all of its files and pushed the new version – in that case the previous version of that commit (commit object, tree object and blob objects for every file) becomes loose and can be deleted. However, for the sake of performance Git just inserts the new objects and doesn't always delete the old objects straight away. Instead, it runs the so-called garbage collection from time to time, which is a mechanism to identify loose objects and delete them.
Normally garbage collection is triggered automatically when you push commits to your repository, however it doesn't happen on every push because GC is potentially quite expensive operation, especially when the repository becomes large. Our Git configuration has some heuristics around when and what kind of GC to trigger (it has several levels of "aggressiveness").
Under normal circumstances, any loose objects will eventually be deleted as long as you keep working on the repository by making new pushes. But for some time Bitbucket would show a larger repository size than it actually is.
Hope that explains why it happened!
Have a good day,
Ana
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.