Repo size bigger than actual

[friglob]

From what i have read, to clean the cache of repositories (and reduce the size of the repo to close as actual), technical assistance is required so i would like to request one.

Thank you

[Ignacio Ampuero]

Hey!

As seen on this forum usually the Atlassian team members can run garbage collection (gc) on certain repos under request here. 

That's the operation you need to resize the "hidden" size of your repo.

[Mark C]

Hi @friglob

Welcome to the community.

Could you provide the repository size of the repository where the size is bigger than actual?

Regards,
Mark C

[friglob]

Hello Mark, it is currently on about 450MB, it should be much less since node_modules/ are ignored and there are no media files.

It is a private repo so please let me know the next steps for the garbage collection that Ignacio mentioned below.

Thank you in advance,

kind regards

[Mark C]

Hi @friglob

I've run Git GC against the repository.

However, the size remains the same.

For that, 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  

Please let me know how this goes.

Regards,
Mark C