<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=388106) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal Empower users to get around the scenario of when branches/tags are unavailable in the commit detail view.  ### Possible solutions from https://gitlab.com/gitlab-org/gitlab/-/issues/325871#note_1236001893 About the “Project has too many branches to search” tooltip, how can we help users if they want to know this information? For example, can we give them a `git` command to return this information locally, showing that in a drawer or modal? From https://git-scm.com/docs/git-branch#\_notes, is `git branch --contains [<commit>] --merged [<commit>]` appropriate? The best solution is to mitigate the problem in the first place, allowing us to retrieve this information on large projects, as @tlinz mentioned in https://gitlab.com/gitlab-org/gitlab/-/issues/325871#note_1096324279, but we should try to guide users to a solution in the interim, if we can. <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->