Accessing the commit in UI by its short SHA1 should result in displaying a list of matched commits

Current situation:
If a customer tries to display a commit using a short SHA1 hash like this: https://my-server/projects/PROJ/repos/repo-slug/commits/ed2af and the short SHA1 is matching more than one commit a 500 error is thrown.

Expected situation:
A list of matching commits is displayed as links containing the full SHA1 linking to the commits.