Last week we were getting warnings that the size of our repo was greater than 1Gb etc. No action was taken but the warnings have stopped and a recent review of our space usage shows the repo just under 0.5 Gb.
I'm curious whether anybody else had a similar situation and if it was possibly an erroneous warning on Bitbucket's part.
Hello @Leschke, Scott ,
Welcome to the Community!
Most likely someone who worked on that repository accidentally included a large file in their commit and pushed it up, but then realised that and amended or deleted that commit effectively removing that large file from repository's. history. Bitbucket was showing the warning in the timeframe between a push that contained a large file and the moment when Bitbucket triggered garbage collection. Being potentially expensive operation, GC isn't triggered after every push, so the warning might've stayed longer than the the repo was actually large.
Hope this helps. Let me know if you have any questions.
Hi everyone, The Cloud team recently announced 12 new DevOps features that help developers ship better code, faster ! While we’re all excited about the new improvements to Bitbucket ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event