4 ms·
definitely. hobbyists tend to run to "lots of small repos with low activity on any given one", but the net resource usage is the same as or lower than "a few bi
by zem 14y ago
definitely. hobbyists tend to run to "lots of small repos with low activity on any given one", but the net resource usage is the same as or lower than "a few big repos". per-repo pricing is more a "pay not to be inconvenienced" than "pay for your use of our resources" thing.
- buddydvd 14y agoFor the many-small-repo scenario, I use this technique to host multiple projects under one Github private repository: http://stackoverflow.com/questions/1384325/in-git-is-there-a-simple-way-of-introducing-an-unrelated-branch-to-a-repository http://stackoverflow.com/questions/1384325/in-git-is-there-a... Instead of creating a repo per project, I create a orphan branch within a shared repo for that project. The benefit of this approach is that you can always cleanly export the commits into its own repository without altering SHA ids. The con is that you have to pick separate branch names for each project (e.g. proj1-master, proj2-master).