3 ms·
Bits might be bits, but you aren't paying for storage. If you are, just get a 1TB hard disk for $50 and have more space than you'll ever need for repos. You're
by StavrosK 14y ago
Bits might be bits, but you aren't paying for storage. If you are, just get a 1TB hard disk for $50 and have more space than you'll ever need for repos.
You're paying for Github, and it's not priced by bits stored.
- derefr 14y agoI think the idea is that all the stuff Github gives you scales pretty much linearly with the number of bits you're storing. Bigger repo = longer commit history; more commits = more issues tracked, more features, bigger wiki, more forks, etc. When you split a project into two subprojects that are fairly equal in scope, each one will likely get just about half of the number of tickets/wiki articles/forks made that the original would have. So making a new repo isn't adding overhead for Github in any marginal way; the overhead would be there either way, as long as that original repo was being used to do the work of two sub-projects.