Currently, doing a global search for code shows the corresponding project name. For commits, that piece of information is missing so the user isn't able to distinguish commits from project to project.
Proposal
Stay consistent with the issues search results and add the namespace/project reference under the committer info:
Edited
Designs
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related or that one is blocking others.
Learn more.
Valery Sizovchanged title from Elasticsearch global search should group commits by project just like we do for code. to Elasticsearch global search should show project names on commits result page just like we do for code.
changed title from Elasticsearch global search should group commits by project just like we do for code. to Elasticsearch global search should show project names on commits result page just like we do for code.
Right now we're just re-using the project commit partial, so unconditionally adding it would be a bit strange. Do we just want it to look something like:
[ avatar ] GitLab Org / GitLab Test: Add Fuubar[ ] Robert Speicher committed a year ago
?
I'm not sure how much sense it makes to visually group by project - how would we reconcile that grouping with the search result scoring?
Yeah, we're reusing the template from regular commit search, but it's not intended to be used for a global search. So I'm not certain about how it should look like but it should be clear where exactly any particular commit has been found.
username-removed-626804changed title from Elasticsearch global search should show project names on commits result page just like we do for code. to Show project names for commit search results with Elasticsearch global search
changed title from Elasticsearch global search should show project names on commits result page just like we do for code. to Show project names for commit search results with Elasticsearch global search