<!--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> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=580609) </details> <!--IssueSummary end--> ## Summary As discussed in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/211102#note_2886293843, we should review existing finders for group::source code that don't use the database for fetching and consider relocating them to avoid triggering unnecessary database reviews. ## Background Currently, finders that interact with Gitaly (not the database) are located in `app/finders/`, which triggers Code Owners database review requirements. This creates unnecessary review overhead for changes that don't actually touch the database. Non-database finders should be moved to `lib/` as recommended in https://gitlab.com/gitlab-org/gitlab/-/issues/366631#problem. ## Proposed Action 1. Identify all finders in `app/finders/` owned by ~"group::source code" that interact with Gitaly instead of the database 2. Evaluate whether these finders should be relocated to `lib/` following the pattern of `RefsFinder` 3. Assemble a list of finders that needs to be moved 4. Create an epic with follow-up issues to track the relocation of identified finders ## Related Issues - https://gitlab.com/gitlab-org/gitlab/-/issues/366631+