Git GC not executed by Bitbucket

[POiD]

Hello,

I cleaned up the size of the larger repositories in my workspace over a month ago, so as to avoid the new 1 GB limit issue.

However, yesterday I see my workspace has been placed in read-only mode even though the actual size was reduced.

I would have expected bitbucket to fix their internal processes prior to actually locking out accounts, but I guess that is too much to expect.

Please execute garbage collection on the repositories in my workspace, at least the one's greater than 20 MB.

[Ben · Accepted solution]

G'day!

Welcome to the Bitbucket Cloud community :)

I've just executed a gc against your largest repositories - and I can confirm that you are now below the 1GB limit (632MB/1GB)

• 890mb > 400mb

• 637mb >2.6MB

What has likely happened, is that a user has accidentally pushed back old refs which have inflated the size again. Please ensure that you and your colleagues perform a fresh clone of those repositories (Quant*******/Iso***********).

Cheers!

- Ben (Bitbucket Cloud Support)

[POiD]

Thank you Ben for performing the gc.

This wasn't due to another user, as I'm the only one working on these projects and the same person that performed the manual clean up. When I performed that clean up the sizes on bitbucket cloud were not updated and the GC was obviously not run. No matter what I tried I could not force bitbucket cloud to perform the gc. The bitbucket help topics and FAQs also do not speak to a way to do so, as I referred to them all many times.

If there is a way, please let me and the community know.

So I thought to "wait a month" and hopefully some automated process would perform it.

Obviously there is no such automated process as it was never performed, until you manually did it. Thank you for your intervention in resolving the immediate issue.