How to create a kind of ''unlisted'' type of repository? #22040
-
|
Is there a way to create a public type of repository that is only accesible to the person having the link to it?, but it wont appear on search results at the site, just like in youtube for example for unlisted videos. Thank you in advance. |
Beta Was this translation helpful? Give feedback.
Replies: 59 comments 25 replies
-
|
No, at the time you can’t create unlisted repositories (altough this probably will be logged as a feature request). Please note you can, however, make a private repository and then invite people who have read-only or read-write access if you have a paid account. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @noxuz, Thanks for this feedback! We’re always working to improve GitHub and the GitHub Community Forum, and we consider every suggestion we receive. I’ve logged your feature request in our internal feature request list. Though I can’t guarantee anything or share a timeline for this, I can tell you that it’s been shared with the appropriate teams for consideration. Please let me know if you have any other questions. Cheers! Andrea |
Beta Was this translation helpful? Give feedback.
-
|
Unlisted repositories will be very good to have. For example, I want to share a URL to my assignment with my teacher. I don’t want to make my repository public, because other students can just Google it and plagiarize. I don’t want to make my repository private either, because I don’t know exactly who will be marking my assignment, so I don’t know whom to invite. Even if I know the person who was marking my assignment, they might not have a github account. So having an “unlisted” type of repository (similar to unlisted Youtube videos) will be very helpful. It will be nice for those repositories to have a long unguessable URLs, like https://github.com/USER/73a90acaae2b1ccc0e969709665bc62f. Thanks. :slight_smile: |
Beta Was this translation helpful? Give feedback.
-
|
+1 Our company has a lot of private repos and some public ones. We maintain a repo named “userscript” full of useful userscripts our teams can use. Some of these scripts are useful to people outside of R&D, and having them create a GitHub account to access them is a deal-breaker. We made this repo public so everyone in the company can use it, but now it appears on our company’s GitHub page. We put a warning in the readme, but having an option to completly hide it from that list would be very useful. Cheers,
|
Beta Was this translation helpful? Give feedback.
-
|
Currently going through this exact situation and surprised it’s still not a feature. I’m having to keep it private till the day of the deadline, at which point I’ll make the repo public, but it’s something I really shouldn’t have to do. |
Beta Was this translation helpful? Give feedback.
-
|
For smaller things like school projects using secret gists (see https://gist.github.com/) may be an option. They are git repositories, and according to the documentation hidden from search engines. |
Beta Was this translation helpful? Give feedback.
-
|
+1, this feature should be added |
Beta Was this translation helpful? Give feedback.
-
|
+1, this is great for sharing simple things with collaborators without GitHub. |
Beta Was this translation helpful? Give feedback.
-
|
+1, interviews are asking for a direct link to code only, and I cannot share school project code publicly! |
Beta Was this translation helpful? Give feedback.
-
|
+1. This seems like the perfect feature for use cases where you want to share code of a “not ready for prime time” nature (job interviews, school projects, etc). |
Beta Was this translation helpful? Give feedback.
-
|
+1, was looking for this as well. Would be nice to have this to prevent polluting one’s repos, but link to it from an issue as repro steps in another repo. |
Beta Was this translation helpful? Give feedback.
-
|
+1, this would be very useful for interviews / job applications to not leak proprietary source code. |
Beta Was this translation helpful? Give feedback.
-
|
+1 This is very important! |
Beta Was this translation helpful? Give feedback.
-
|
+1 this is very useful |
Beta Was this translation helpful? Give feedback.
-
|
I would love this feature |
Beta Was this translation helpful? Give feedback.
-
|
Please add this. I am considering switching away from GitHub to self-hosted. |
Beta Was this translation helpful? Give feedback.
-
|
It's not as hood as a real solution, but for hosting issue reproduction this works pretty well: https://craigory.dev/blog/2024-09-11/gh-unlisted-repos/ |
Beta Was this translation helpful? Give feedback.
-
|
yaaaay 🎉 |
Beta Was this translation helpful? Give feedback.
-
|
Just use BitBucket for the repos you don't want to have listed. Having them public there is almost as good as an unlisted repo on GitHub ;) |
Beta Was this translation helpful? Give feedback.
-
|
gitfront.io works well |
Beta Was this translation helpful? Give feedback.
-
|
+1 i want unlisted repos |
Beta Was this translation helpful? Give feedback.
-
|
+1 for unlisted 😢 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
I would like to have an unlisted repo to send my portfolio pet-project to potential employers without getting it exposed to web crawlers and used to train AI. An average employer wouldn't go through the process of being added as a read-only contributor to the repo, and that's why the unlisted functionality would be a great solution for such a scenario. GitHub is the best place for it as everyone knows its' interface. Quick and easy access by a target audience only is a key here. Please, add it! 🤩 |
Beta Was this translation helpful? Give feedback.
-
|
+1. A developer's GH account often serves as a resume, where you don't want your most recently worked-on repos to be random cruft that you were playing around with. However, making your repos fully private limits them in other ways besides just visibility in the GUI. My use case is this: I'd like to clone my random-cruft experimental repos onto various slapdash servers that I may spin down again soon. I don't want to add SSH keys for these servers to my account, since I'm just running quick experiments - I don't want to have to think about security, appropriate permissions, or having to manage those keys in the future. I'd just like my repo to be publicly accessible via git, but also not have to think about my peers and potential employers seeing these quick and sloppy experiments as my most recently worked-on repo. Unlisted repos give us a tasteful layer of semi-privacy. Like a little gate on a short picket fence around a garden. It's not about hardcore security here, it's about giving us the tools to just make things nice and presentable. Thanks. Edit: SourceHut's UI is comically rough looking, but they have an Unlisted option. And by default it gives you one URL for read/write and another for read-only. Works fine, seems like a good place to do quick-and-dirty projects you're not wanting to present to others. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Almost 7 years later..... |
Beta Was this translation helpful? Give feedback.
-
|
okay, common someone, anyone at GitHub reading this. |
Beta Was this translation helpful? Give feedback.
-
|
I'll probably repeat myself again, but unlisted repo would really endow a freelance developer to share the code via links on platforms such as Buy Me a Coffee. The feature would be game-changing, and may attract more people going forward with this platform, however I see GitHub core team turned a blind eye on this for unknown reason, sadly... 🥹 |
Beta Was this translation helpful? Give feedback.
-
|
Well, it has been 8 years since the feature request was "shared with the appropriate teams for consideration.", it seems like they have no intentions of implementing it. :) |
Beta Was this translation helpful? Give feedback.
No, at the time you can’t create unlisted repositories (altough this probably will be logged as a feature request).
Please note you can, however, make a private repository and then invite people who have read-only or read-write access if you have a paid account.