when fuzzy-finding, grouped repositories is a bit confusing

Is your feature request related to a problem? Please describe. @nickcraver tweeted me this screenshot a few days ago:

Note that Chat - the project that Nick wants and the best match - is actually below other matches because grouping still takes precedence over the fuzzy-find results when we’re filtering.

Describe the solution you’d like I’m not settled on a solution for this, but random thoughts:

• once fuzzy-finding kicks in, maybe we drop the grouping of repositories? But that throws away the grouping which might confuse people in a different way.
• can we rework this UI so that we don’t do the normal grouping, but still keep that context around?

Describe alternatives you’ve considered Not really, just writing this up to capture it.

Teachability, Documentation, Adoption, Migration Strategy 🤷‍♂️

[vinkla]

I agree with #7769 that the new filter updates makes it harder to jump between repositories.

1. When I filter the list I would expect it to sort exact matches before repositories in the recent group.
2. When I press <kbd>Enter</kbd> I would expect it to jump to the first repository in the list.

Example 1

In this case I want to jump to the atom-ide-definitions repository. Though, I’ve recently worked in the autocomplete-tailwind repository. When I filter “atom” it returns autocomplete-tailwind before atom-ide-definitions. I would expect it to list the atom-* repositories first.

Example 2

In this example I filter dotfi but the atom-ide-definitions repository is still listed before the dotfiles repository.

[shiftkey]

How about ordering the groups based on the weight of the best match in the group?

Maybe? I think we’d need a spike branch with some dummy repository/account data to experiment with from a UX perspective, to figure out what makes sense.