Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,555,480
Community Members
 
Community Events
184
Community Groups

Request For Garbage Collection

Edited
zachredfern
zachredfern Mar 29, 2023

Hello,

I have a repository approaching 4GB in space and would like garbage collection performed on it.

This repository also has an upstream that I would like cleaned as well.

The workspace is called "******" and the last few characters of the repository in question are "**"

Thanks for your time,

Zach

Answer
Watch
Like kennethlam likes this
124 views

1 answer

1 accepted

0 votes
Answer accepted
Ben
Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 29, 2023

G'day Zach!

I've censored all parts of the workspace/repo identifiers just in case given this is a public forum.

I located both the fork repo and the upstream repo based on your description and have executed a gc operation against both of these, the new sizes are as follows:

  • Fork: 3.4GB > 301.3MB
  • Upstream: 2.5GB > 121.3MB

NOTE: Yourself and your colleagues will need to perform a fresh clone of both of those repositories, this will avoid any possibility of pushing back old refs and inflating the size again.

Hope this helps!

Cheers!

- Ben (Bitbucket Cloud Support)h

Reply

Suggest an answer

Log in or Sign up to answer
Bitbucket
Bitbucket
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events

See all events