Don't forget easy access to all the code to train Copilot, the AI code launderer. With my tinfoil hat on: even the private repo edition!
And made private repos free after the acquisition https://github.blog/2019-01-07-new-year-new-github/
There's a 100MB limit on the size of a push, which also limits the size of a any single git object (i.e. file) to 100MB too. However GitHub supports LFS for large files, and their documentation says to use LFS for files over 100MB:
https://docs.github.com/en/repositories/working-with-files/m...
> GitHub blocks pushes that exceed 100 MB.
> To track files beyond this limit, you must use Git Large File Storage (Git LFS).
https://docs.github.com/en/billing/managing-billing-for-git-...
According to my own GitHub account ( https://github.com/account/billing/data/upgrade?packs=1 ), I'm paying $37/yr for 600GB LFS storage on top of my existing GitHub Pro subscription.
I'd love to know how you managed this! I'm paying $60/yr for 50GB, which feels exorbitant.
The source you link is 2 years old.
Yes, the information is 2 years old, but since nobody has any proof of the contrary, I'd say it still stands.
(Sorry, my upload is too slow to just do a quick check and see if I can indeed push a 100gb repo, maybe someone else can try?)
For comparison, I think GitHub just have a cap of 100MB on any single individual file, plus:
> 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. If your repository excessively impacts our infrastructure, you might receive an email from GitHub Support 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.
Which is a bit wishy-washy, but sounds like there's room for discretion / exceptions to be made there rather than a hard cap at 5GB.