Forums

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

BitBucket repo size

time June 5, 2025

Dear BitBucket Support,

 

In my Repo I have limit from 8 GB and we reached 6.79 GB but suddenly we can't able to push any code now, starting from Monday.

Here is screenshot from what I am seeing on our Repo:

image (51).png

Can you please share what is the problem and what are the option related with this?

Thanks in advance

1 answer

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

Hi @time 

The reason you're being blocked is due to changes that were announced in a blog post and via email concerning changes to the Free plan - which restricts the workspace size limit to 1GB:

You have a very large repository in your workspace (6.8GB) that is contributing to this size limit. I've just gone ahead and executed a garbage collection to attempt to reduce the size of this, but it did not reduce.

You have a couple of options to resolve this:

Option 1 - Delete & recreate the repositories
This is the fastest way to solve the problem, but loses metadata such as PRs, Pipelines, Permissions, etc.

1. Perform a clone of the repository for backup purposes

2. Delete that repository from your workspace to free up space and allow you to push. NOTE: This will permanently remove metadata such as PR's/pipelines/user permissions etc.

3. Identify the largest files in your repository by executing the following command:

git rev-list --objects --all \
| git cat-file --batch-check='%(objecttype) %(objectname) %(objectsize) %(rest)' \| awk '/^blob/ {print substr($0,6)}' \
| sort -r --numeric-sort --key=2 \
| numfmt --field=2 --to=iec-i --suffix=B --padding=7 --round=nearest

3. Perform cleanup operations locally to reduce the size

4. Once complete, push those repositories back to your workspace by creating a blank repository with the same name of the deleted repository, then mirror pushing the contents of the cleaned repository:
HTTPS
git push --mirror https://<username>@bitbucket.org/<WorkspaceID>/<RepoName>.git
SSH
git push --mirror git@bitbucket.org:<WorkspaceID>/<RepoName>.git

NOTE: This will remove metadata such as PR's/pipelines/permissions etc but will keep your commit history and binary files intact.

Option 2 - Temporarily upgrade

1. Upgrade to a paid plan and utilise our 30-day trial period to restore functionality and provide more time to reduce your repository directly without deletion. You can choose to continue or cease your trial before the end of the 30-day period.

2. If you encounter any issues during this period - you may raise a ticket directly with our support team using your workspace URL: 
https://support.atlassian.com/contact/ 

Please let me know how this goes.

Cheers!

- Ben (Bitbucket Cloud Support)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events