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
Hi, @ChuckieAJ! Thank you for reaching out to Atlassian Community.
I found the repository that was showing 1GB on your workspace, so I ran the GC against this repo and managed to reduce its size. Just to give you some context, the GC runs periodically on the server, so unless the auto GC has not been run on the server and you reach the repository size limit, the GC is not mandatory.
I also would like to share with you that we have a feature request to allow users to mark repositories for git GC, as you can check here:
Please consider adding yourself as a watcher to receive the updates as we make progress with this. If you are not familiar with our Feature Request Policy, you can read more about it here.
Feel free to share any additional questions or concerns regarding this case.
To compress means here with reference to git is to optimise the size of the repository
What you can do is perform a git gc from local and force push the repo to remote repository
Here's the guideh ttps://support.atlassian.com/bitbucket-cloud/docs/reduce-repository-size/
But this is the thing - I understood that free users can't raise support tickets any more. I know for fact that when Atlassian staff compress my projects they dramatically reduce in size. Yet when I had the email about being unable to raise support tickets this was understandably an area of concern for me.