I'm trying to use Github as a place to keep my work and show potential employers. Would love to still have the ability to make it private and just give people access to view.
+1 - I have a couple of private repositories I want to share with friends but I don't want them to be able to write to them.
+1 Extending this string, because of the work I do with public repos, it would be nice to be able to directly invite people to watch some public repos directly through github (as opposed to email or twitter), without giving them write access. Maybe this is already possible?
+1 on read only access
The ability to view and not modify a private repository would be very valuable to our organization.
I just went to add a collaborator to a private project with read-only access and was surprised that I couldn't do it.
+1 I want to show the code I have done from edX courses to potential employers, but I can't make them public due to edX's honor code, It would be usefull to have a way of granting by an URL, view only permission to a private repository, just like in google drive for example.
That's kind of an obvious need in my view.
My specific situation is I'm freelancing and want to give read access to my client.
I just discovered the option of private repositories in the announcement. Just like stated, I use them to 'apply for a job'. That's even the only usage I make of them, besides experimenting with Git and Github.
So, I would like to selectively give access to people, like by supplying an URL with a key. As I know from photo albums on the web. This should be ready only, which may include copying or cloning, preferably copying.
So that is my request, which seems pretty obvious to me.
By the way, I do not consider this 'solved'. That is more of an euphemism to get rid of the question.
It seems to me that the git/GitHub owners, by assuming that there is only one use-case for git/GitHub (shared open software development), are limiting the usefulness of GitHub. Some of the postings in this thread show other use cases that require readonly access to files for one audience yet require pulling/pushing/versions/branches to the developers.
An additional use case that occurs to me is using GitHub to make a portion of a proprietary product public. We always assume that a product is either proprietary or open, but not both. But I can easily imagine products that are proprietary and sold for profit, yet contribute a new and useful subroutine or algorithm to the Open Software community. In such a case the developers might want to use GitHub to collaborate in private, but might want one specific file to be readonly or read/write visible to the public.