Remote Garbage Collection

Question

A repository I am working on had large files in the commit history causing it to take up a large amount of space in BitBucket. That history has been removed, but I am unable to get the remote repository to recognize it.

Does BitBucket's remote garbage collection run on a schedule automatically, or how do I make that `git gc` happen?

Thanks!

Theodora Boudale · Answer

Hi Ryan,

Thank you for the output. Since the size of the mirror clone is that small, something is taking up space in the remote repo that the git gc I run does not remove. I am going to create a support ticket on your behalf using the email of your community account to investigate this further and try to resolve it.

You are going to receive an email with a link to the ticket. Just in case you don't, please feel free to let me know and I can post the ticket URL here. The ticket will be visible to you and Atlassian staff, no one else can view its content even if they have the URL.

Kind regards,
Theodora

Ryan Dorman · Answer

Theodora,

Thank you again for helping me figure this out. I followed the steps you outlined and here's the output I received:

count: 0
size: 0 bytes
in-pack: 301
packs: 1
size-pack: 21.93 MiB
prune-packable: 0
garbage: 0
size-garbage: 0 bytes

Regards,

Ryan

Theodora Boudale · Answer

Hi Ryan!

Pull requests do not count toward the repository size.

If I understand correctly, the repo now has only one branch (master) and only 1 commit on this branch?

Could you please do the following:

* Take a mirror clone of the repo (git clone --mirror <repo_url>)
* Navigate then inside the directory of the mirror clone
* Inside that directory, execute the command git count-objects -Hv

This command will show info about the repo's size. What output do you get from this command?

I don't have access to your repo to do this myself. I want to see if there is a discrepancy between the size we report and the size you see in a mirror clone to understand where the problem lies.

Kind regards,
Theodora