4 ms·
> To ensure better relevancy, we're being conservative in what we add to the search index. Repository forks will not be searchable unless the fork has more star
by robrenaud 14y ago
> To ensure better relevancy, we're being conservative in what we add to the search index. Repository forks will not be searchable unless the fork has more stars than the parent repository, for example.
This has a grandfathering problem when the maintainers switch. The new active branch of development is overshadowed by the previous branch. I've had someone takeover my project, but I still have 2 years of accumulated stars from when the project was fresh. The new development has less than 1/10 the number of stars as my branch. But I guess fixing this is kind corner case might be left for v2.
- tedunangst 14y agoHave you considered renaming your fork? Like xyz-old? One of the things that annoys (and sometimes infuriates) me about github is identifying the fork I want to be using. A million old blog posts point to the wrong place. If that repo were replaced with a new blank repo saying "moved to here" it'd be a big help.
- robrenaud 14y agoI did change the readme to point to the new mainline development. I still think there might be some utility in having the code as I left it around, so I didn't delete the repo.
- plorkyeran 14y agoDeleting your repo and recreating it as a fork of the new upstream may be a good idea, although it does break the links to all of the other repositories forked from yours. It really would be nice if Github handled this case better.
- dewski 14y agoDeleting and recreating your repo isn't necessary. If there's a problem with your fork not showing up, let us know and we'll look into it.
- arcatek 14y agoDidn't you transfer the ownership of repository ?