Github repos from different orgs should not fold as subresults

xvello The rule at play here is that we "expand" the group into individual results if there are over a certain number of results from the same domain.

@z64 Could this be removed for Github & gitlab domains? While this is reasonable for some sites, it really isn't ideal for GitHub and associates.

z64 Thank you for responding on this 1.5 year old thread! Honestly, both seem fine options to me. I would probably prefer the "user/org" approach, this way it is doing what it is intended to do: Grouping results of the same 'origin'.

Currently, search for pandoc beamer code listing grayscale shows a GitHub repository in the result, with seemingly related issues below it:

However, these two issues are actually in two different repositories than the "alexeygumirov/pandoc-beamer-how-to" repository from the top-level result: Wandmalfarbe/pandoc-latex-template and jgm/pandoc/.

I understand this is the "normal" behavior, i.e. that search results are grouped by domain. It might make sense to consider an exception for GitHub though, where grouping by repositories (with related issues and PRs below) might make more sense.

A user would be able to find issues related to a specific GitHub repository at a glance, instead of having to click onto the issue in the search results.

frereit There is another post that suggests grouping github by repo, can you find it so that I can merge?

Vlad https://kagifeedback.org/d/149-github-repos-from-different-orgs-should-not-fold-as-subresults

I don't think this is actually done? The first result for pandoc beamer code listing grayscale still shows "alexeygumirov/pandoc-beamer-how-to" as the top result with an Issue from "wandmalfarbe/pandoc-latex-template" grouped below it, as if it was an Issue from "pandoc-beamer-how-to":