Having more granular control on private repos for individual users is a must. Sure if they can read it they should be able to clone/fork but i want to disable specific users ability to push with out a propper pull request. Same with branching. Really should be able to have same functionallity as public for private, just we control the viewers.
Using protected branch ( especially for master) will give you some options, such as requesting members with write permission review to the changes before merging. You can also enforce the need for owner review. I did not tried protected branches with private reops before but I think it would be the same as the public repos.
@WaleedMortajaThis is not exactly what you need.
+ 1 it would be nice to have possibly give a look at the private private repository.
Working with a colleague overseas that I want to be able to give access to pull my code (for reference/educational purposes), but not to be able to push.
+1 from me.
I would like to be able to invite someone to "ONLY look" at a private repo.
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.