Mismatch in size between bitbucket and local clone

[matthew_reeve]

Good morning,

I have tidied up one of my repos which was excessively large, by creating a new branch, moving a snapshot across, and then removing the old branch with the no longer needed history.

This has been force pushed, and I noted a dramatic drop in size after a short delay (presumably while the GC ran) from 3.2gb to 0.9gb.

However, when cloning locally, even with a full set of the content extracted (and not just the .git folder) - I am only seeing 0.3gb, which is closer to my expectation.

When running git count-objects -v on the freshly cloned repo, I get the following :-

git count-objects -v
count: 0
size: 0
in-pack: 1097
packs: 1
size-pack: 85064
prune-packable: 0
garbage: 0
size-garbage: 0

The repo in question within my account is az*_dep*

I do not have any pull requests that could be holding a lock on any files.

I would appreciate any advice you can provide, or any further GC that can be run on your side to keep me well below the 1gb limit for this repo.

Many thanks

Matt

[Theodora Boudale · Accepted solution]

Hi Matt,

I ran a git gc on this repository and its size has been reduced.

Does it look ok now on your end?

Kind regards,
Theodora

[matthew_reeve]

That's fantastic - down to <100mb now, which is closer to what I was expecting. Thank you for such a swift action!

[Theodora Boudale]

You are very welcome! Please feel free to reach out if you ever need anything else!

[Rilwan Ahmed]

Hi @matthew_reeve ,

Welcome to the community !!

I have requested Atlassian support for the GC. An Atlassian Support Engineer will review the post and respond on this thread within 2 business days.

[matthew_reeve]

Thanks Rilwan, much appreciated.