6 ms·
You can't actually put the Android source in GitHub because of the 4GB per repo size limit. Niche problem, but shows the scale of things.
by ajb 4y ago
You can't actually put the Android source in GitHub because of the 4GB per repo size limit. Niche problem, but shows the scale of things.
- ajb 4y agoAs people have pointed out, there's not a hard 4GB limit. They do recommend less than 5GB.
- naikrovek 4y agopaying customers and popular open source repos can go well beyond 5GB. GHEC customers have a 5GB limit per file in git-lfs.
- saagarjha 4y agoYou could if someone contacted GitHub to have it mirrored.
- naikrovek 4y agoit's not a real limit.
- est31 4y agoWDYM by 4GB size limit? When I run du -h on my linux checkout, I get 6.4G (no build artifacts, just git tracked source code plus the .git directory). Even if I only look at the .git/objects directory, it's 5.2G large.
- deleted 4y ago[deleted]
- londons_explore 4y agoIt seems GitHub have whitelisted git projects containing certain commits or files to go over the size limit. Chromium is also well over the size limit.
- _wolfie_ 4y agoCan you use this to work around the size limit by having linux source code (up to the required commit) in a orphan branch?
- londons_explore 4y agoIf I were implementing it, I would say total total repo size limit = 4GB, excluding any objects part of commits in whitelisted projects. That makes sense for GitHub, because what they really care about is the hard drive space you use up, and a repo containing a commit they are already storing for some large project is no additional disk space.
- 1letterunixname 4y agoLol. That's tiny. Monorepos of MAANGs are multi TiB.
- naikrovek 4y agoI have repos in GitHub Enterprise Server which are WELL OVER 100x what you say the limit is. There is not a technical limit of 4GB per repo on github.com. maybe a private repo size limit if you are not a paying customer, but it is not a technical limit of the platform, I assure you.
- fanf2 4y agoThere is a 4GB limit on a single push, but you can work around that by pushing a very large repository incrementally. I have done that in the past for a repo with a linear history: push the first N commits, then the next N commits, etc. It would be harder for a repo with many refs or a branchy history; maybe limit each push by commit date?