<!--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=17059) </details> <!--IssueSummary end--> ### Description When CI fails after a commit (edit of a file) It should be easy to navigate to an edit of that file. Currently it takes five clicks to get there. One of these is selection of the proper branch -- and such selection is prone to errors. Currently, the commit link provided does NOT go to the commit with the problem file(s). It goes to a branch for that commit. This is NOT a place where the file(s) can be edited and fixed. What is shown is something like this:  In this case I was editing on the `master` branch. I expected that the commit link for dc203fb7 would take me to where I could fix the problem. I am not sure what the branch-related commit is used for. It does not take me anywhere I see as useful. Perhaps others rely on that for something. ### Proposal When CI indicates failure a link to the relevant commit -- or to a clickable list of file(s) involved in the commit should be immediately available so a user can start to debug/fix whatever caused the failure. /cc: @JobV