Bitbucket Repository Size Mismatch After Reducing Objects

[Elumalai Shanmugam]

Despite reducing the repository size locally (as shown by git count-objects -v indicating a size of 494 KB), Bitbucket still displays the repository size as 3.8 GB. This discrepancy suggests that stale or unnecessary data may still be present on the remote repository or that Bitbucket’s repository size calculation hasn’t updated correctly.

Expected Result: The repository size displayed on Bitbucket aligns with the local repository size (494 KB).

Actual Result: Bitbucket reports the repository size as 3.8 GB, which is significantly larger than the local size.

[Brant Schroeder]

@Elumalai Shanmugam Welcome to the Atlassian community

Per the support article here: https://support.atlassian.com/bitbucket-cloud/docs/reduce-repository-size/#Garbage-collection-is-automatically-run-to-delete-dangling-commits  Garbage collection probably needs to be run.  You can submit a support issue with Atlassian making this request.  If you are on a free plan let me know and I can escalate it to Atlassian here.

[Ben]

Hi @Elumalai Shanmugam 

I've just executed a gc against your repository which has reduced the size from 3.8GB to 570KB.

I can confirm that your total workspace size is only 302.4MB which is well within the 1GB limit that will be enforced in April:

• https://www.atlassian.com/blog/bitbucket/important-changes-coming-to-bitbucket-clouds-free-plan

Cheers!

- Ben (Bitbucket Cloud Support)