You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We pushed a big folder accidentally. Then we ran BFG and removed that folder. Now a local copy is around 1.4 gb, but the size shown by bitbucket is 3.89GB.
What else can I do, or should a gc be run on the repository by the Bitbcuket team?
Hello @Alexandrun and welcome to the Community!
After cleaning up a repository and pushing it back to Bitbucket, it's necessary to run a garbage collection on Bitbucket side to remove the dangling objects that were left behind by the removal of the large files.
I went ahead and executed a GC in the repository of your workspace that matched the size you shared with us. The size was reduced back to 1.3GB :)
Now that GC is completed, I would highly recommend you having everyone on your team removing their old copies of the repository and doing a fresh clone of it. Since the old clones have a dirty history, it's better to delete them, so you don't risk pushing the dangling objects back into your cleaned repository, which would increase its size again.
Thank you, @Alexandrun !
Thanks a lot for your answer. The GC on your side can be run only by the Bitbucket team or is there an option that I can also do it in the future if we make the mistake again?
Hey @Alexandrun !
The GC is run automatically by bitbucket from time to time, but in cases where you want it to be expedited, you can let us know here in the Community and we can help execute it for your repository.