GitHub is a popular platform for hosting and collaborating on software projects, but it’s important to understand the limitations when it comes to repository size. While GitHub offers a generous amount of storage, there are specific limits in place to ensure the platform runs smoothly and efficiently for all users.
File Size Limits
One of the most critical size limits on GitHub is the maximum file size allowed in a repository. If you attempt to add or update a file that is larger than 50 MB, you will receive a warning from Git. GitHub blocks pushes that exceed 100 MB for a single file. To track files beyond this limit, you must use Git Large File Storage (Git LFS), which is a separate extension designed to handle large binary files.
Repository Size Limits
While there is no hard limit on the total size of a repository, GitHub recommends keeping repositories under 1 GB for optimal performance. If your repository exceeds 1 GB, you may receive an email from GitHub Support asking you to reduce its size. Additionally, GitHub has a soft limit of 5 GB per repository, and if you exceed this limit, you may receive a warning email.
Pushing Large Repositories
GitHub also has a limit of 2 GB for a single push. If you attempt to push a repository larger than 2 GB, you may encounter errors such as “fatal: the remote end hung up unexpectedly” or “remote: fatal: pack exceeds maximum allowed size.” To work around this limit, you can split your push into smaller parts, each under 2 GB in size, or delete the Git history and start from scratch.
It’s important to note that while GitHub provides tools and extensions to help manage large files and repositories, it’s generally recommended to keep your projects within reasonable size limits for optimal performance and collaboration.