<!--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=538959) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal While GitLab currently recognizes co-authors in the commit body and displays the avatar and a link to the profile, it does not display co-authors on the commit interface. That means that users have to expand the commit body to be aware that an co-author was involved. This feature is supported on GitHub, where contributors listed in the `Co-Authored-By` section are shown as co-authors of the commit. Implementing this functionality in GitLab would enhance collaboration transparency and give proper credit to all contributors. The requested feature would: - Parse the `Co-Authored-By` trailer in commit messages. - Display co-authors in the commit details view. - display name - display combination of both user icons - Enhance the user interface for better collaboration recognition. #### Example from Github  #### Possible visual representation for Gitlab  In this example only the user names are combined but not the icons (s. Github Example) ### Related Issues https://gitlab.com/gitlab-org/gitlab-foss/-/issues/31640 <!-- 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: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->