My repository reported a size over 2GB and I started to remove larger files from the commit history by using the suggested BFG tool.
The tool reported a successful run and the repository seems to be significantly smaller locally. But whenever I try to trigger the remote garbage collection the repository seems to grow rather than shrinking in size.
I tried several different methods (from the atlassion post and from SO) but nothing seems to be working.
Thank you for reaching out to Atlassian Community!
I ran the GC against your repository that was above 2 GB and was able to reduce its size to 235.6 MB.
Just to give you some context around this behavior, after you push the changes with BFG, the remote repository still has the old references as well. So the GC is required on the remote repository to clean up any old references you have removed.
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.
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...
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
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events