<!--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=345466) </details> <!--IssueSummary end--> ### Update the _<clone url>/info/lfs/locks_ endpoint to get more information on the lock owner We are using the lock feature in GitLab. '_git lfs locks_' command is showing all the locked files and the name of the lock owner. But this info **is not enough to uniquely identify the owner**. So it would be great if the command can give more info on user ex. 'name (email)' format. An alternate approach is - If we update the full name for GitLab user profile in 'name (email id)' format then the console returns the same for '_gi lfs locks_' command, but I think an update at the endpoint is a better solution Impact : We are working with lot of lfs files and its some extra effort to find the actual lock owner. Thanks, Geevarghese