Fix broken repo error raised after requesting a commit

Prevents a 500 error on screen after Rugged::RepositoryError: Could not find repository from '/var/opt/gitlab/git-data/repositories/user/project.git', which could happen when checking for the last commit in the list of projects (dashboard).

Related https://gitlab.com/gitlab-org/gitlab-ce/issues/20501

Added 1 commit:

• 55ad046e - fix throwing error finding commit on an empty repo

Added 1 commit:

• 55051ebf - update version and changelog

Added 1 commit:

• 6170aa15 - Commit.find return nil no longer throws an error on an empty repository

Unmarked this merge request as a Work In Progress

Added 1 commit:

• 26bce16b - fix wording

Added 1 commit:

• 7e4bde8f - Commit.find returns nil and no longer throws an error on an empty repository

Reassigned to @rymai

@rymai can you review this one? I still have to add another small fix to CE related to this. Also, not sure who's got access to push the gitlab_git gem? So I can then update the version in gitlab-ce...

@jameslopez Thanks, LGTM!

Status changed to merged

Mentioned in commit fc105f0d

@rspeicher Could you tag v10.6.7? Thanks!

@rymai Done.

@rspeicher Cool thanks!

@rspeicher Could you actually push the tag to Rubygems? :) /cc @jameslopez

@rymai Done, sorry to forget!