-
Notifications
You must be signed in to change notification settings - Fork 395
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Github specific: forked repositories are not currently searchable. #58
Comments
I'm not sure if this is fixable on my end but I'll look for a solution :/. I wonder what happens if we shut down the original project. |
See https://help.github.com/articles/searching-repositories/ for information on how to include forked repositories in search results. By default github doesn't search forked repositories. |
heres a short update - http://stackoverflow.com/a/33666719/112050
|
:/. I'm not sure what to do here. I'll try to find somebody from Github to see if there is another way. It is unlikely to have as many stars in this project any time soon. |
I think its time for jobqueue to break away from Path ! May I suggest renaming it with a cool name - Square always has good names. On Fri, Dec 25, 2015 at 1:24 AM, Yigit Boyar [email protected]
|
I've contacted support and they detached the project. It is searchable now :). And in V2, i'm probably changing the package name since I rewrote most of it, I'm breaking some bad APIs (with better replacements) and I might as well break the package :). |
and I may as well re-name it but not sure about Rope or Lace :/. |
awesome! really excited to see what you come up with. |
@yigit - can you please pick a name quickly ? most of us are deferring upgrade until you set the name. we would rather not refactor twice ! |
@yigit name suggestion Haberdashery
|
I'm having trouble searching your repo for any code, references, etc. because Github throws a message saying "Sorry, forked repositories are not currently searchable. You could try searching the parent repository. "
Could you figure out how to fix this please ?
The text was updated successfully, but these errors were encountered: