diff options
author | Douwe Maan <douwe@gitlab.com> | 2016-02-19 11:00:58 +0300 |
---|---|---|
committer | Douwe Maan <douwe@gitlab.com> | 2016-02-19 11:00:58 +0300 |
commit | cb0b7de48267abee85d39571ae55a0e988cc21eb (patch) | |
tree | 9794c86a84893fa20b730ff6b185d0067f413630 /config/application.rb | |
parent | c58a02e82f7448babe341d782af1455ab2b15774 (diff) | |
parent | f3b6839a4add7c74dd864dbdf016f5bc3fa7216a (diff) |
Merge branch 'fix/project-forks-page' into 'master'
workaround for forks with an invalid repo
Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/13465
The error occurs when a project returns a `nil` commit for a variety of reasons, I assume the repository is corrupt - perhaps as a result of a failed fork.
With this MR, we do not show forks with corrupted repos in the list of forks, as this does not seem to work anyway. A better solution is to fix the cause of the issue and/or any data integrity problem...
Also fixing Sentry issue: 1180
`undefined method 'already_forked?' for nil:NilClass `
See merge request !2836
Diffstat (limited to 'config/application.rb')
0 files changed, 0 insertions, 0 deletions