Workspace in read-only mode due to exceeding the 1GB limit

[AlejandroBurgos]

Hi! The limit was exceeded after submitting a commit, and the workspace went into read-only mode. Some obsolete repositories were deleted to reduce the space, but the workspace remains in read-only mode and won't allow me to push.
I tried reducing the repository space according to the documentation, but the workspace remains in read-only mode.

I don't know if there's something I'm missing to disable read-only mode.

By the way, several of my repositories take up significantly more space than my local project.

[Phil C · Accepted solution]

Hi @AlejandroBurgos

Welcome to the Bitbucket Cloud community!

Earlier this year, we shared updates about the Free plan through a blog post and email. These changes include limiting workspace sizes to 1GB. You can read more about this here - Important changes coming to Bitbucket Cloud’s free plan

Currently, your workspace is hosting several repositories, and their total size is 1GB. Which is at the workspace size limit.

You have two ways to resolve this issue:

Option 1:

• Upgrade to the Standard or Premium plan.

Option 2:

• Reduce the sizes of the repositories in your workspace. This route will involve working with you via a ticket.  
• Delete additional repositories.

As long as the combined size of all your repositories is under 1GB, you will be able to push again.

I hope this helps.

- Phil

[SuttonTim]

Can you give some indication as to how long it takes from deleting data to the workspace being writeable again, please?

[Syahrul]

Hey @SuttonTim 

If you delete a repository, the size update occurs instantly. However, deleting data within a repository depends on whether the automated garbage collection (GC) is running. Sometimes, we need to trigger GC manually. If that’s the case, please create a new community thread so we can assist you with manually triggering GC.

Regards,
Syahrul