Need GC on remote

[adrianklimczak]

Please run garbage collection on our Survival Defender repository.

We have trimmed old history to reduce the repository size and did
$ git push --all --force

Size of the repository on BitBucket is 1.89 GB, while the actual size is much smaller:
$ git count-objects -v
count: 0
size: 0
in-pack: 47156
packs: 1
size-pack: 990471
prune-packable: 0
garbage: 0
size-garbage: 0

[Caroline R · Accepted solution]

Hi, @adrianklimczak, 

Thank you for reaching out to Atlassian Community!

I ran the GC against your repository and managed to reduce its size.

To give you some context around the git GC process, Bitbucket triggers a garbage collection on the repository after each push, however aggressive GC is triggered by GIT once the unreachable/dangling objects become older than 30 days.

For this reason, there is no need for us to trigger a manual GC for your repository. However, we are happy to run it for you if you feel there is a need. 

We already have a feature request to allow users to mark repositories for git GC, as you can check here:

• https://jira.atlassian.com/browse/BCLOUD-11593

Please consider adding yourself as a watcher to receive the updates as we make progress with this. If you are not familiar with our Feature Request Policy, you can read more about it here.

Feel free to share any additional questions or concerns regarding this case.

Kind regards,
Caroline

[Gabriel Hillesheim da Silva]

Hy, I ran BFG over my repo, push all the files I've cloned with '--mirror', when I type 

"git count-objects -v"  I get this 

count: 3
size: 3
in-pack: 1607
packs: 1
size-pack: 68472
prune-packable: 0
garbage: 0
size-garbage: 0

But in BitBucket size information still warning me about the size.

'<Repo name>' is repo name

Can you take a look?

[Nic Brough _Adaptavist_]

You'll need to talk to your administrators about this, we have less access to, or knowledge of, that system than you do.