To make sure we can provide the most stable service possible to our users, we are putting in place new size limits for both Git repositories and Git files. Starting September 2020, pushes to the repository will be blocked if these size limits are exceeded.

Why we’re creating size limits for Git

As most seasoned users of Git understand: Git just isn’t that great at managing large files, such as audio, video, or high-quality images. The more large files your repository has, the longer your processing latency. Regular processes like git clone, git push, and git pull can start to feel like they take an eternity.

We want Backlog to perform well for all of our users. And when too much server space gets unnecessarily taken up by large files and repositories, it can negatively impact Backlog as a whole.

What are the new size limits?

Maximum file size is 100MB

Each file size will be limited to 100MB. If the file size exceeds the limit, you will receive an error message and the push will be blocked.

Maximum repository size is 10GB

The total repository size will be limited to 10GB. You will receive warning messages as your repository size grows to ensure you’re aware of approaching any size limits. Eventually, if the repository size exceeds the limit, you will receive an error message and the push will be blocked.

Note: You can still git clone and git fetch even when exceeding size limits.

What if you already exceed the limit?

In September 2020, we will apply the new limits to all new repositories. If an existing repository already exceeds the new limit, we will reach out to you via email about reducing it.

For now, repositories created before September 2020 that exceed the new repository limits will remain available. But we will likely require them to fit these new limits in the foreseeable future.

Things you can do to reduce file and repository sizes

If you are regularly pushing files of 100MB or more

Files that have already been pushed will still be available for download after this limit is applied. But you won’t be able to push those files anymore. Luckily, there are a few helpful solutions for reducing files sizes in Backlog:

• Git LFS lets you easily push files larger than 100MB to your Git repository. Read more about how to use it in this help article.
• Shared File lets you continue to manage files larger than 100 MB. Read more about how to use it in this help article.

Note: Shared File doesn’t maintain versions like Git.

If your repository size is about to reach 10GB

After applying this limit, any pushes that exceed 10 GB in repository size will be blocked. If your repository size is about to reach 10GB, you should remove large files from the repository to reduce the size of your repository.

Note: You cannot reduce repository size by simply deleting a large file from the latest commit. The files from past commits exist in the repository as a snapshot. That means you’ll have to go back and delete files from past commits, too.

Thank you for working with us on this change

We understand that some users will need to dedicate a bit of time to reduce their repositories and put in place new ways of managing larger files. We apologize for any inconvenience this may cause.

We look forward to bringing you a faster, more stable Backlog with these size limits in place. And we appreciate your understanding greatly.