Forums

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

Garbage Collection Request

Martin Wadeson
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

Hello, we have some repos that need garbage collection to help us use less space.

 

Could I ask you to perform some garbage collection on the server side please.

 

git reflog expire --all --expire=now

git gc --aggressive --prune=now

1 answer

0 votes
Tansu Akdeniz
Community Champion
June 5, 2025

Hi @Martin Wadeson 

Welcome to the community!

The Atlassian support team has been notified and they will reach out to you.

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

Hi @Martin Wadeson 

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

  • 568mb > 560mb

  • 321mb > 296mb

  • 151mb > 95mb

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
PERMISSIONS LEVEL
Product Admin Site Admin
TAGS
AUG Leaders

Atlassian Community Events