nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why does repo size under Repository Details not match the size of .git directory?

asperry

I just recently used git-filter-repo to remove large files from my repositories history. I went from over 300 MB to about 1 MB. I force pushed the repository and now when I clone it, I get the smaller (filtered) repository, but on the Bitbucket website under "Repository Details" the size still says over 300 MB. I pushed the filtered repository several days ago. Why does the website still say the size is so large when the size of the cloned repository is clearly much smaller?

Accepted answers

All comments

Fabio Racobaldo _Catworkx_

Hi @asperry ,

welcome to the Atlassian community!

Probably because your large files are in the history of your repo so, even if, they are not in the actual repo , they are in the previous commits yet.

In order to remove large files you need to rewrite repo history, otherwise git just keeps the large file in the history.

Take a look to the following article https://support.atlassian.com/bitbucket-cloud/docs/reduce-repository-size/

Hope this helps,

Fabio

asperry

Thank you for your reply, but this does not answer my question. As I mentioned in the original question, I have already changed my repository history using git-filter-repo which is recommended over BFG or filter-branch. The repository that I clone does not contain the large files in the history. My question is why the size given on the Bitbucket website does not reflect that I have reduced the size of the repository by changing the history.

Caroline R

Hi, @asperry, welcome to the community!

As you confirmed you removed some large files from your repository history and force pushed these changes to your remote repo, I believe the remote still have some dangling commits that need to be removed with a GC. In this case, I can run a GC on the remote repo to remove any dangling commits there, In order to do that, I just need to know the repo name. Could you please share the workspace_ID/repository name masked with asterisks here so I can identify it?

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

Kind regards,
Caroline

asperry

That would be great! We're not up against any size limits as far as Bitbucket is concerned so there's no rush if Bitbucket periodically runs GC on some infrequent interval. My question was more based in curiosity and a desire for numbers to agree.

I'm not sure what you mean by sharing the repository name masked with asterisks. Do you mean give a portion of the name but use asterisks for the rest?

Caroline R

Hi, @asperry, yes, this is what I meant

Kind regards,
Caroline

asperry

I have two repositories that would need GC. They are:

utahtelerobotics/rob************** and utahtelerobotics/cap**************

In the future, do I need to request GC, or is it something that's done automatically at some interval?

Thanks!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud