How I can trigger garbage collection manually, as I already made remove of the dangling commits
Hi @time
I don't believe there's a native feature for this - there's a feature request though, which has a workaround listed on it. Check that out here: BCLOUD-11593
You should also be able to request GC from Atlassian Support - contact them here: https://support.atlassian.com/contact/#/
Ste
@Ste Wrightthanks for your reply, but I am using plan and unfortunately I can't do directly, maybe from Atlassian Support will answer here, or please if you know someone please tag in this loop and maybe I will be helped.
Thanks in advance
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'll mention it to them :)
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
G'day!
It is correct that it is not possible to manually trigger a garbage collection from your side. There is an automated process which will execute a gc based on a certain threshhold of garbage (ie dangling commits, unpacked refs) is reached.
I have raised a support ticket in our system for you, as we will need access to your repository in the backend to execute a gc on our side (and this requires a formal ticket for authentication purposes). Usually we can do this without a ticket, but the size has not reduced based on our automated tooling so we will need to investigate this further.
Cheers!
- Ben (Bitbucket Cloud Support)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.