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.
Existing features (including lack of forced PR's) for private repos don't make this any better than hosting a repo on any number of other services.
+1 Please add this feature for a developer account. Btw if I add Collaborators to my private repo, then can they push to any branch or create any branch on github?
+1 Here too. I'm kinda astonished this hasn't been implemented yet. You should be able to create a unique, read-only, guid-like link to your private repo similar to what you can do with files in OneDrive. This is a no-brainer.
+10000 my organization NEEDS this, we have different teams, support teams, testing teams, and some are outsorced... we don't want them to have access to ALL of the code, only to give us feedback about testing results and Issues about the applications, etc..
+1. Youtube allows publishing a video that is only accessible via link. Not private per se, just "unlisted". I need to share repos with online classmates for peer review, but I don't want my beginner code in a new language to be publicly available.
Sorry, but this issue is not solved.
This is a tremendous security issue! Especially since Github is promoting the idea of machine users for servers which need to access multiple private repositories, it makes sense to allow for collaborators to be read-only. As the documentation says as a PRO: "Anyone with access to the repository and server has the ability to deploy the project." -> meaning anyone with access to the machine user account or the server can deploy and break all other servers (yes, we live in a world with cloud computers where we may have multiple instances running at the same time, accessing the same repos).
Clone, fork, fine but not push. That should be read-only by default for any collaborator!
For those who cannot post professional code publically, temporary read-only access to private repos would be a perfect way to share code during the job search process. Allowing prospective employers a view of your work, without allowing them access to the code. I am really surprised this has not been implemented. Perhaps I am just missing another way to achieve this?