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; } } }

Repo size: remains the same after deleting large files

Alexgijutsu

Hi! I deleted a good number of large files from a repo, but the size still remains the same. Would it possible to run garbage collection on it? It's the GameLit repo and it's 822.4 MB.

Thanks, Alex

Accepted answers

Samuil Enchev

Hi @Alexgijutsu,

I understand this issue must be frustrating for you. I've created a support ticket on your behalf - BBS-256073. Please keep an eye on your email for updates, and we're here to help you through this.

Best regards,
Samuil

All comments

Viswanathan Ramachandran

This needs server side GC. I have reported to support team.

Samuil Enchev

Hi @Alexgijutsu,

Best regards,
Samuil

Trevan Householder_Isos-Tech-Consulting_

Hi @Alexgijutsu , @Viswanathan Ramachandran and @Samuil Enchev are right that Atlassian has to run GC on Cloud . One catch: if the files were deleted in a normal commit, they're still in your Git history, so GC alone won't shrink anything.
You'll need to rewrite history first. Make a mirror backup, strip the big files with BFG or git filter-repo (e.g. --strip-blobs-bigger-than 50M), force-push, then let support know so they run GC afterward. Have everyone re-clone, too, or an old clone can push the files right back.
Atlassian's full walkthrough is in Reduce repository size.