Forums

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

Clean Up My Repos

Ware Works
June 10, 2026

Due to some old non required files, I am not able to push anything from my local and having > 1gb issue which I think should not be there. 

 

Please increase size temporary or clean the files from the repo.

2 answers

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

Hi @Ware Works 

The 1GB workspace restriction was introduced some time ago, Free workspaces are limited by this restriction.

I have executed a garbage collection against your repository on the server-end, but it has only reduced the size down from 3.3GB > 2GB.

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

  4. Perform cleanup operations locally to reduce the size

  5. 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: Atlassian Support  

Cheers!

- Ben (Bitbucket Cloud Support)

0 votes
Arkadiusz Wroblewski
Community Champion
June 10, 2026

Hello and welcome to the Community @Ware Works 

Have you already tried to do it yourself with BFG Repo-Cleaner or git filter-repo ? 

If doing it yourself fails, let me know, we can then escalate it further for remote GC.

Best,

Arkadiusz 🤠 

Ware Works
June 10, 2026

yes it is failing. I tried to do it and nothing works except getting the same exception - git : remote: This workspace is over the 1 GB size limit. Reduce the size of your workspace or upgrade to a Standard or Premium plan to increase the size limit.
At line:1 char:47

remote: Upgrade to a Standard or Premium plan: https://support.atlassian.com/bitbucket-cloud/docs/manage-your-plan-and-billing/#Change-your-plan
remote: Or learn how to reduce your repository size: https://support.atlassian.com/bitbucket-cloud/docs/reduce-repository-size/#Rewind-history-to-undo-large-commits.

Ware Works
June 10, 2026

Local cleanup already successful:
• Removed .vs/ and Backup/ folders from entire history
• Local .git directory is now only 2.97 MB
• Attempted force push to Development branch
Issue: Bitbucket is still rejecting the push with:

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