Descobrir sua cota em disco

Limites para tamanhos de arquivo e repositório

To ensure good performance for our users, we recommend repositories be kept under 1GB each. Keeping repositories small ensures that our servers are fast and downloads are quick. If your repository does exceed 1GB, you might receive a email from GitHub Support asking you to reduce it.

Repositories have a hard size limit of 100GB. If you reach 75GB, you'll receive a warning from Git in your terminal the next time you push a change. In addition, we place a strict maximum size limit of 100 MB for individual files in a repository. Para obter mais informações, consulte "Trabalhar com arquivos grandes".

Backups

Git is not designed to serve as a backup tool. However, there are many solutions specifically designed for performing backups, such as Arq, Carbonite, and CrashPlan.

Descartes de banco de dados

Version control systems, such as Git, are not designed to handle large SQL files. To share large databases with other developers, we recommend using Dropbox.

Git shouldn't be used to backup your production servers. For more information, see "Backups."

Dependências externas

External dependencies can cause Git repositories to become very large. To avoid filling a repository with external dependencies, we recommend you use a package manager. Popular package managers for common languages include Bundler, Node's Package Manager, and Maven. These package managers support using Git repositories directly, so you don't need pre-packaged sources.

Versões de lançamento incluídas

Não recomendamos distribuir código compilado e versões predefinidas no repositório. For more information, see "Distributing large binaries."

Alterar o histórico de um repositório

If you already have a repository that's quite large, you can reduce the size of a repository by removing large files from the repository's history. For more information, see "Removing files from a repository's history."