How to reduce the remote repo size after deleting large files

Bob Seed

Good morning,

I've recently performed a repository cleanup using git-filter-repo to remove large files from our repository's history:

Actions Taken:
1. Created a mirror of the repository
2. Used git-filter-repo to remove specific large files and folders
3. Force pushed the cleaned repository back to Bitbucket
4. Verified the local repository size is now 460MB
5. Made a fresh clone of the remote repo to confirm this

Current Situation:
- Local repository size (verified with git count-objects): 460MB
- Bitbucket's reported repository size: 2.5GB
- The discrepancy persists even after several days
- It seems the cleanup was successful locally, but Bitbucket's size hasn't updated

Request:
Could you please:
1. Trigger a manual garbage collection on our repository
2. Verify if there are any old pack files or artifacts that need cleanup
3. Update the repository size calculation
4. Assist me with further instructions on how to reduce the remote repo size

Thanks,
Bob

Phil C_66l19w

Hi @Bob Seed,

Welcome to the community! 

I've run garbage collection on the largest repository on your workspace, and the repository size has reduced to 460.6 MB. Is this the size of the local repository?

You can check by running the following command on the local repository: 

 git count-objects -vH

The "size-pack" will show the local repository size.

Before proceeding with the next push to the remote repository, please ensure that you and all repository collaborators make a fresh clone of the remote repository to avoid reintroducing old/cleaned-up history and potentially inflating the repository size again.

I hope this helps. 

- Phil