> 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…
A Whole New Code Search
31–40 of 113 posts
Re: A Whole New Code Search
#32It's just a shortcut for searching the current repository you are viewing (by adding a search box next to the tag count).
Re: A Whole New Code Search
#33Re: A Whole New Code Search
#34> 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…
Have 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.
Re: A Whole New Code Search
#35Re: A Whole New Code Search
#36I'll be really pleased if this works in a usable manner, I'd very much given up on search in github.
Re: A Whole New Code Search
#37Re: A Whole New Code Search
#38Re: A Whole New Code Search
#39very nice. one bad setting (perhaps a default that never got overridden) is that searching for foo_bar searches for foo and bar separately, rather than treating foo_bar as an indivisible token.