Feature request: Add unlisted repositories

[cmarshall108]

Add the ability to make repositories unlisted, meaning that these repositories are not listed under your account and are only viewable by users who are given links. For example, this would be very similar to that of unlisted Youtube videos...

[FullofQuarks]

This behavior already exists for private repos. You can then give read/write permissions for collaborators. In the case that you mean there exist a special link in which a user would be able to have full read/write (similar to YouTube), what would be the use case?

[cmarshall108]

My use case is i was applying for a job, they wanted to see source code from my previous projects. I did not want to open source the source code due to unrelated reasons... But i wanted the folks at the company to be able to read over my source code without having to have specific read/write permissions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

[lunny]

If we could generate an encoded URL for a private repository which has an expired time, and then you can share it with others.

[cmarshall108]

Yeah that would certainly work.

[TheRealJP]

Is this still being added?

[miki725]

Another use-case is schoolwork. Submitting a link to a repo Professor can access without either creating account or making the repo public. Would be very useful if this feature is added.

[ivi9901]

I find this pretty usefull when you want to share something with someone that doesn't have an account, without having to make the source code searchable. The miki725 use-case is one of the best I can think of.

This is already added in gogs. I'm talking from the ignorance, but it might be possible to port that idea from there.

[6543]

thoughts: I would implement it as another visible level ... Private, Limited, Unlisted, Public

so for why nobody has implemented it ... to do this properly ... you have to refactor a lot :/
more explisit: rewrite the acces model for orgas&repos + migration

[a-hurst]

Chiming in here for another use case: occasionally the makers of specialized scientific hardware share their source code with researchers, but don't explicitly license it or post it publicly themselves.

If your team has a customized/patched version of that software, you can't exactly post it openly on GitHub or another searchable public repo, but you often still want to be able to share the code with others and deploy it easily on new machines. Unlisted repositories would solve the issue completely.