Forums

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

Repositorie size is bigger than 1 gb but is not true

Quickets
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 5, 2025

I have this message in my BitBucket Panel "Your workspace has exceeded the 1 GB limit and has been placed in read-only mode. Learn more about upgrading your plan and checking storage usage."

I have deleted some branches , but the repositorie size doesnt match with the size that bit bucket panel says.

I cannot push my code until i reduce the size to 1GB or less.

How could i delete the branches or reduce the space, if i did it and doesnt change anything?

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 @Quickets  

 

I have attempted to reduce the size of your largest repositories by executing a garbage collection, but it has not reduced the size much, and your workspace is still > 1GB:

  • 1.3GB > 1.3GB

  • 2.4GB > 2.0GB

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 those repositories for backup purposes

2. Delete those repositories 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 repositories 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