Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-11593

Allow users to mark repositories for git gc (BB-13894)



    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.



      You can enable an experimental feature to trigger GC automatically next time you accidentally push a large commit and go over the Hard size limit.

      Do this by clicking on your profile icon and selecting Labs, then enabling the feature "Delete dangling commits when over size limit". This only affects your personal login, meaning that auto GC will be triggered only on the repositories part of your personal workspace and it won't be triggered on the repositories part of any shared workspace. Tell your team in case they want to try it out too.

      Next time you accidentally push large files to Bitbucket, follow the user guide to reset the branch to just before the large commit. When you force push that refs-only change, the Labs feature will automatically run GC to immediately remove the large commit.

      This should bring your Bitbucket repo below the size limit, allowing you to push commits again without having to raise a support request. Anyone else using the same repo who has pulled the large commit will need to create a fresh clone.

      Note that this won't work if your repo goes over 5GB. In that case your repo is put into read-only mode and you will need to request help from our support team at https://support.atlassian.com/contact/.

      we need a process to initiate git gc runs on server repositories.

      one of our repository grew to Hard size limit and it is read only for quite some time. We would need to bring attention of bitbucket team to near-the-limit repositories without getting tech support involved.


        Issue Links



              d74c65c84d35 Prasad Satam
              legacy-bitbucket-user Legacy Bitbucket Cloud User (Inactive)
              624 Vote for this issue
              394 Start watching this issue