Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Update workspace quota after freed up space

Fabio June 6, 2025

Hi everyone. I exceeded the 1GB Workspace limit so I deleted some big old repositories. I was wondering if there is a way to update the disk quota so I can continue make all the commits I have to do! Thank you!

3 answers

0 votes
Fabio June 7, 2025

You were right, I thought I already freed up enough space. I'm cleaning now.

Can I ask you why there are some repo where the size of the effective files is like 50MB and there is a .git folder of about 100MB? Is there a way to free up this space?

Phil C
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 9, 2025

Hi @Fabio ,

It's not uncommon to see a discrepancy between the sizes of your working files and the .git folder in Git repositories. Here are some reasons why this occurs and how you can reduce the size of the .git folder:

Reasons for the Large .git Folder:

  • History: Git retains the entire project history, which can expand over time.
  • Large Files: Deleted large files are still kept in history.
  • Binary Files: These files (e.g., PDF, JPEG, etc...) are less compressible, resulting in increased file size.
  • Reflog and Unreachable Objects: These items can accumulate, taking up additional space.

Ways to Reduce Size:

  • Prune Unreachable Objects: Execute git prune to eliminate objects not associated with any branches.
  • Garbage Collection: Use git gc to remove unnecessary files.
  • Delete Unused Branches: Remove branches that are no longer needed using 'git branch -d <branch-name>', and then run git gc again.
  • Rewrite History: Tools like BFG Repo-Cleaner can help eliminate large or undesired files from your project's history. Exercise caution, as this approach alters commit history.

Important Tips:

  • Backup: Always create a backup of your repository before making significant changes.
  • Team Coordination: Inform your team before rewriting history, as this impacts everyone involved with the project.
  • Remote Updates: After cleanup, you'll need to perform a force push (git push --force) to refresh the remote repository.

- Phil

0 votes
Phil C
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 6, 2025

Hi @Fabio,

Earlier this year, we provided an update regarding the Free plan through a blog post and email. These updates involve a 1GB limitation on workspace sizes. More details can be found here - Important changes coming to Bitbucket Cloud’s free plan.

Your current workspace includes numerous repositories totaling 1.2 GB. As you continue to work on these repositories and potentially add more, the overall size could further exceed the limit.

To address this issue, you have two options:
Option 1:

  • Upgrade to the Standard or Premium plan. (This is the simplest option that allows for growth without hitting the workspace size limit.)

Option 2:

  • Reduce the sizes of the repositories in your workspace. This method would require collaboration through a ticket.
  • Consider deleting additional repositories if possible.

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

I hope this information is useful.

- Phil

0 votes
Pat C June 6, 2025

I have the same problem - I can't commit due to the repo being locked for being over-quota. It's a fun catch 22...

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin Site Admin
TAGS
AUG Leaders

Atlassian Community Events