Run Garbage Collection

[Buannic Arthur]

Hi,

Our team just sadly discovered the 4Gb size limit on a repository, as well as the 1Gb size limit for LFS files (on Free plan)

We have since cleared our entire history (all commits, tags and branches), ready to start versioning again from scratch, but our git commands are still frozen from the repository (which wrongly considers itself above the 4Gb limit)

We didn't find any option to manually trigger the garbage collection logic (though from other topics here, we gather it simply does not exist), and have struggled with removing our LFS remaining files (we could delete those 1 by 1, but we have like 500+ and removing them all that way seems... inconvenient)

Any help in this situation would be very welcome!

Thanks in advance

[Syahrul]

G'day, @Buannic Arthur 

Welcome to the community!

I have triggered Git GC on the affected repository, and it has been reduced to 1.1 GB. Please review them and let me know if this is the expected size?

Regards,
Syahrul

[Buannic Arthur]

Hi !

Thanks a lot for the fast response and Git GC :), although as you may have guessed our repository still weighting 1.1 GB sounds a bit weird since it only contains a 1kb Readme file

At first I thought it may have been caused by our non-cleared LFS artifacts, but those two storage seem independent (we've begun clearing the LFS remnants and the repo size does not reduce). I'd be curious if you have insights as to where that Gb of excess data comes from?

(I'd also like to point out that having to clear LFS files 1 by 1 is really inconvenient, having at least the option to bulk clear would definitely help)

[Syahrul]

Hey @Buannic Arthur 

I have raised a support ticket on your behalf to continue the investigation. You can view the ticket at our Suppor portal.

Regards,
Syahrul