Repository ize increased to 2.9 GB due to large historical files

[Abinaya Ramaiah]

We are experiencing an issue with our Bitbucket Git repository where the repository size has grown to approximately 2.9 GB.

After running the following command locally:

git count-objects -vH

we observed that the large size is primarily due to Git historical objects (blobs) stored in the repository history, rather than files in the current working directory.

Observations:

Working directory size is normal.

Large files appear to have been committed in the past.

unable to Git clone 

CI/CD pipeline execution time has increased.

Repository performance is degraded.

Troubleshooting Performed:

Checked repository size using Git commands.

Identified large blobs in Git history.

Reviewed .gitignore to prevent future large file commits.

Assistance Required:

Best practice to safely reduce repository size.

Whether Bitbucket provides any server-side cleanup options.

Any risks or recommendations before rewriting history and force pushing.

This issue is impacting development workflow and pipeline performance. Kindly provide guidance on the recommended resolution.

[Syahrul]

Hey @Abinaya Ramaiah 

Welcome to the community.

I am unable to locate the affected repository. Could you please raise a support ticket with us here and provide the URL of the affected repository so we can advise you on how to reduce its size?

Alternatively, you can also check our KB below on how to manage and reduce large repositories.

https://support.atlassian.com/bitbucket-cloud/docs/reduce-repository-size/

Regards,
Syahrul

[Tansu Akdeniz]

Hi @Abinaya Ramaiah 

Welcome to the Atlassian community!

The Atlassian support team has been notified and they will reach out to you within two business days.