The 2GB limit is not just to fend off abuse. It is also in place as Git and Mercurial aren't terribly well designed to deal with large repositories and files. Performance generally suffers as repositories grow exceptionally large.
As a consequence, we do not sell higher repo limits.
Typical scenarios where repos grow large involve projects that contains binary assets (as opposed to just code/text). Some commit their dependencies, while game projects often have gigabytes of artwork.
While these use cases are normal, Git and Mercurial aren't very suited to managing them and the recommended way to deal with this is generally to try and decouple binary assets from the code. For instance, using a dependency management system instead of committing dependencies.
Changing your workflow and getting files out of your repo in order to reduce its size can be a little tricky. An earlier blogpost discusses some techniques. For the future, we are looking into adopting Git LFS which should make it a little easier to manage binary files.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.