Bitbucket Cloud is implementing a 100 MB limit on files included in a Git push

[#1]

Starting on May 6, 2024, we will begin rolling out a 100 MB file size limit for git pushes to Bitbucket Cloud repositories.

Why are we implementing a push file size limit?

Bitbucket Cloud currently has a repository size limit of 4 GB, which puts a repository in a read-only state if exceeded and requires support intervention to reduce the repository size back below the limit. The most common reason customers exceed this limit is by pushing large files. Customers should be storing large files as Git LFS instead of their repository.

A push file size limit helps customers keep their repositories in the most performant state and below the 4 GB size limit by keeping unwanted files and/or binary files out of source control.

What can I do if I run into this limit?

If you encounter the push file size limit, you have two options:

Option 1 (RECOMMENDED):

Any files included in the push that are over 100 MB can be converted to Git LFS to track them outside of the core repository. Learn more about using Git LFS with Bitbucket Cloud.

Option 2:

If using Git LFS is not feasible, the 100 MB push file size limit can be disabled by a repository admin within the Advanced settings in Repository settings.

WARNING: If this limit is disabled, you are at risk of exceeding the 4 GB repository size limit, which will put the repository into read-only mode and require support intervention to reduce the repository size back below the limit when possible or applicable. This can cause significant disruption to your operations.

What if I already have files over 100 MB in my repository?

This limit only applies to pushes. Any files that are over 100 MB and are already in a repository will not be affected, if they are not modified and included in any pushes. If those large files are being frequently modified, we recommend converting them to LFS where practical or necessary. Learn more about converting existing repository files to Git LFS here.

[ccenvcvb]

Looks like bitbucket.org does not cater for large mono-repos.

Is there a switch to toggle if a repo needs to grow beyond 4GB ?

Not sure if we're close to the limit yet, just curious

[Rich]

We keep getting warnings about going over 2GB and have to contact support to run git gc to re-compress. 

They keep saying they will offer this for the user but I haven't seen the option yet. 

[Sam Nichols]

Hi @ccenvcvb 

To protect platform stability, Bitbucket Cloud maintains limit of 4GB for all repositories. There is not a self serve toggle in the UI to request a repo size increase, and there are no short term plans to implement that.  If you would like expert advise for your specific use case, please reach out to our Support team, sharing your repository URL and your needs, and our team will work with you on the best possible solution.

[水越 直哉]

「File size limits」When will this feature be implemented?

[gny9j7fdzf]

@水越 直哉 "Starting on May 6, 2024..."

[Andreas Rath]

Will there be a API call available to switch off the push limits for all git repos in an organization? 

If yes, would be great if you can post this script here. 

Comment to bitbucket team: 

I would suggest and wish if you can offer to "opt in" to this push limit rather than automatically enforcing it on all git repos. I think this is a nicer way to bring new features to your customers. Would appreciate if you think about this and discuss it internally again. Many thanks!

[Sam Nichols]

Hi @Andreas Rath 

There is currently no API to disable to push size limit. Related to that, it is not recommended to disable the limit for all repositories in a workspace, but rather, only those where Git LFS is not feasible.

If your Bitbucket Cloud workspace is on Standard or Premium plan and you would like help understanding what repositories may be impacted by this change to help you  evaluate whether or not the limit should be disabled, you can reach out to our Support team, who can help identify repositories within your workspace that have recently had large file pushed up to Bitbucket hosted services.

[artiom_buslovsky]

I am still getting same error even with LFS installed