Bitbucket Free workspace over 1 GB – cannot force-push cleaned 159 MB repository

Hi @csibu ,

I've pinged the forum support team to take a look at this and potentially run GC on that repo/workspace. 🛎️
Someone should get back to you within 1-2 business days (usually it's quicker than that).

Cheers,
Tobi

Hi @csibu 

I have attempted to reduce the size of your repository by executing a garbage collection, but it has not reduced the size very much.

The most likely reason is due to the way metadata is stored on the server-end, PR's retain the full size of binary files in order to speed up diff calculation.

As metadata exists purely on the server-side, there's no way to target it with gc operations, and it does not exist locally (hence why there's such a large size discrepancy in local vs remote).

• 2.8GB > 1.5GB

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 the 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 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 if necessary

5. Once complete, push the repository back to your workspace by creating a blank repository with the same name of the deleted repository, then mirror push 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 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 trial period depending on your preference.

2. If you encounter any issues during this trial/paid period - you may raise a ticket directly with our support team using your workspace URL: Atlassian Support  

Please let me know how this goes.

Cheers!

- Ben (Bitbucket Cloud Support)