Hi, Vivek!
I have confirmed that you had 2 repositories above 1 GB, so I ran a git GC on both of them through the server. I was able to reduce the size of one of the repositories, but the other one is still over 1 GB.
Just to give you some context around our repository size limit, we do recommend repositories be kept under 2.0 GB to help ensure that our servers are fast and downloads are quick for our users. Bitbucket Cloud repositories under a paid plan have a 4.0 GB limit. When that limit is reached, you will only be able to push changes that undo the latest commits.
The repository limit for free repositories is 2 GB; however, at this time, we are not enforcing this limitation, but this is subject to change. In any case, considering your repository size now, you shouldn't be blocked. However, we would like to recommend to you the following processes:
- If you have large files you don't need to version, then you can use BFG or git filter-branch to remove them. The following documentation has a very good explanation of how to achieve this:
- If you do need to version large files, you can convert them to LFS by using Git Large File Storage
I also suggest that after whichever conversion you make, and after you run a git GC command locally, check again the local repo size with git count-objects -vH to see if it's a size that's good for you before you push.
If you do this and push to the Bitbucket repo, the Bitbucket repository size will get increased again. No reason for alarm, it will need a git GC from our side for the changes to reflect, so you can let me know after you push.
Please, feel free to share any additional questions or concerns regarding this case.
Kind regards,
Caroline
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.