👋 We've unified all of GitHub's product documentation in one place! Check out the content for REST API, GraphQL API, and Developers. Learn more on the GitHub blog.


Publicamos atualizações frequentes em nossa documentação, e a tradução desta página ainda pode estar em andamento. Para obter as informações mais recentes, acesse a documentação em inglês. Se houver problemas com a tradução desta página, entre em contato conosco.

Descobrir sua cota em disco

GitHub tries to provide abundant storage for all Git repositories, although there are hard limits for file and repository sizes.

Neste artigo

Você conseguiu encontrar o que estava procurando?

Tip: If you regularly push large files to GitHub, consider using Git Large File Storage (Git LFS). For more information, see "Versioning large files."

Limites para tamanhos de arquivo e repositório

To ensure performance and reliability for our users, we actively monitor signals of overall repository health. Repository health is a function of various interacting factors, including size, commit frequency, contents, and structure.

We recommend repositories remain small, ideally less than 1 GB, and less than 5 GB is strongly recommended. Smaller repositories are faster to clone and easier to work with and maintain. Individual files in a repository are strictly limited to a 100 MB maximum size limit. Para obter mais informações, consulte "Trabalhar com arquivos grandes".

If your repository excessively impacts our infrastructure, you might receive an email from Suporte do GitHub asking you to take corrective action. We try to be flexible, especially with large projects that have many collaborators, and will work with you to find a resolution whenever possible. You can prevent your repository from impacting our infrastructure by effectively managing your repository's size and overall health. You can find advice and a tool for repository analysis in the github/git-sizer repository.

Observação: se você adicionar um arquivo a um repositório por meio de um navegador, o arquivo não poderá ser maior que 25 MB. For more information, see "Adding a file to a repository."

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."

Você conseguiu encontrar o que estava procurando?

Pergunte a uma pessoa

Não consegue encontrar o que procura?

Entrar em contato