Comments on: github pricing

By: Mark Brown

Mark Brown — Thu, 24 Dec 2009 17:00:19 +0000

Having worked with this for a while it actually appears that the duplicate detection stuff doesn’t quite work – it looks like what’s happening is that content pushed up that is also present in the origin repository (eg, merges down of upstream code) are getting counted as space usage.

By: broonie

broonie — Wed, 21 May 2008 09:25:34 +0000

Thanks. For the space usage you probably want to make it clearer how the space is accounted – it’s not at all clear that you only count differences in your billing, especially once you get onto stuff like merging in other repositories. Will this only work if you explicitly fork from within github or will the server figure out relationships otherwise?

I saw the commenting stuff – that wasn’t present at the time I wrote the post.

By: PJ Hyett

PJ Hyett — Wed, 21 May 2008 03:49:16 +0000

I know I’m a little late to this post, but I thought I’d set the record straight for anyone that happens to read this.

1) When you fork a repo, we only save your differences from the source repo.

Meaning, when you fork github’s mirror of the kernel (http://github.com/github/linux-2.6), the space you’ll use is negligible (< 1MB).

2) We also provide commenting on source files and diffs which works as a really interesting code review tool.

Read more about it here: http://github.com/blog/42-commit-comments