<!--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=32047) </details> <!--IssueSummary end--> ### Problem to solve When exploring an unfamiliar codebase, it's hard to find the most important/relevant files. ### Intended users * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) ### Proposal Add a visual indicator that shows how many times each file/folder has been changed relative to other files/folders in the repository. Here's one idea:  The prototype above was created by adding a `background-image: linear-gradient` CSS rule to each `.tree-item` table row, for example: ```css background-image: -moz-linear-gradient(left, rgb(255,255,255) 0%, rgb(230,230,240) 35%, rgb(255,255,255) 0%); ``` ### Further details There are probably a few different ways we could determine a file's relative "popularity score". Perhaps the most obvious/simplest would be to count the number of commits that have involved the file. For folders, the score could simply be the sum of all its children's scores. I'm not sure how feasible this is from a performance perspective, though.