Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
After rebasing and doing a git push -f, the size of the repository gets larger every time. I have observed this behavior on both Bitbucket and Beanstalk. Every time I do one of the fast forward push, it seems that my 400k repository becomes 800k, then 1200k.
I trie doing git gc --aggressive locally and then doing git push -f, which didn’t seem to reduce the remote repository size.
Any suggestions?
You’ll basically have to wait for your remote provider to decide to gc for you. You may want to access commits referred to by the SHA1s now not pointed to by any history accessible from a branch (or e.g. maybe a pull request refers to those commits, even if the branches have been deleted).
You may be able to contact the customer service and get them to do this for you, as I know e.g. GitHub has this option (as it’s exposed in the admin interface in github:enterprise).
There may be some automated trigger for this if you approach your size limits.