Addition to message #21:
Another use case for fine-grained permissions is when a commit concerns a security problem. The changed files in such a commit should be visible only to the author and to those who manage security updating. In case it isn't obvious, the reason is that making these files readonly or read/write might leak compromise information to malicious users when the repository access is public.
Also, it might be helpful to note here that the Google Gerrit Code Review process and tools, built on top of git, already provide such fine-grained permissions, but at the expense of a very detailed workflow as compared with either git or GitHub.
Guess there arent any news in this subject right? is there an open ticket to implement the feature at least? What alternatives are you using? I really dont want to duplicate my repos, plus downloading is different from consulting
Our product team is definitely discussing new features to make collaboration of different types easier on GitHub. However, nothing on this front has shipped as of yet. Any new features will be announced in the GitHub Changelog, so I'd recommend keeping an eye on that page for updates.
As for collaborating on projects where you want someone to be able to work on a portion of the codebase but not the entire codebase, it might be worth breaking your codebase into smaller, reusable pieces. Then you could add someone as a collaborator on a repository that only has access to the smaller piece of the whole and you can use continuous integration to make sure that changing code in one piece doesn't break the overall codebase.
Hope that helps!
Yea.. that was my next question, if it was possible to restrict users to certain folders.
I came up with some workarrounds to fix these problems
4 months later and I see nothing about this feature on the Changelog. So having read-only access to a private repo is not in our future? What service are developers using to show their private work to prospective clients?
Would be VERY useful to be able to share a URL (and key?) for read only accesses
As some have mentioned. I have clients that would like to review my code, but still limit their access to specific files/folders. And the same for private code that could be shared with potential clients to give them an idea about the quality of work that can be provided, and so on.
If perhaps there were permissions for specific files/folders with a timeout option. That way, there wouldn't be a need to revoke permissions at a later date.
The "Solution" is not a solution though :( It's just an explanation of the current system which does NOT have the requested feature. Glad I'm not alone in needing (not wanting) this feature!
Hi everyone, apologies if this is repeating a topic discussed already.
Can I give read-only access to my private repo, to someone who is not a collaborator at present? Can I share a url, or add someone as a read-only collaborator? I don't want to give fork/clone/download rights.
I have a Developer account at present (not a Team/Business account, so cannot structure an organization-based acess). Here are the types of Github accounts. Thanks.
I think it is a good idea to add a read-only permission that allows a developer to share a URL of his code to an employer for example during a technical test.
Please implement this feature (including Github Enterprise)! Thank you.