Grouping global searches by unique org/repository

[lsegal]

Most of the time when I am performing searches I am much more interested in the number of results across unique codebases than I am in the individual search. As an example, I might be trying to answer a question like, "how many Ruby codebases use :nodoc:?", or "how common is the acts_as_paranoid gem?"

Currently code search seems to provide a very greedy per-repository search results, in other words, for a given term it will list every matching file in a given repository, sorted by repository popularity.

While this might make sense for one specific type of search, the practical implication of this is that pretty much every global language specific search is currently enumerating the files of the most popular repository of that language. Here's a bunch of random word searches in the Ruby language, all pointing to pages of results almost exclusively from rails:

It would be great to have global searches group per-repository results, otherwise you are basically just doing a rails repository search whenever you search anything globally for Ruby; and I'm sure this probably applies to other languages with a single extremely popular org/repo.

[colinwm]

Hey @lsegal, thanks for the feedback. We've just made some ranking improvements to increase the diversity of resullts. Let me know what you think!

Here's an example of some search results for a query you provided with our new ranking scheme:

[SoKamil]

@colinwm, while this is useful, this doesn't solve the problem entirely. I'd like to search for repos which uses certain library, but have no duplicates. This way I could learn how many usages are there in the wild and be sure that I didn't open same repo twice when looking for usage patterns.

[azitabh]

Having this as a feature would be very useful.