Name |
Last commit
|
Last update |
---|---|---|
.. | ||
admin | ||
dashboard | ||
explore | ||
group | ||
profile | ||
project | ||
shared | ||
snippets | ||
abuse_reports.rb | ||
groups.rb | ||
invites.rb | ||
login_form.rb | ||
search.rb | ||
snippet_search.rb | ||
user.rb |
BigW Consortium Gitlab
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
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
admin | Loading commit data... | |
dashboard | Loading commit data... | |
explore | Loading commit data... | |
group | Loading commit data... | |
profile | Loading commit data... | |
project | Loading commit data... | |
shared | Loading commit data... | |
snippets | Loading commit data... | |
abuse_reports.rb | Loading commit data... | |
groups.rb | Loading commit data... | |
invites.rb | Loading commit data... | |
login_form.rb | Loading commit data... | |
search.rb | Loading commit data... | |
snippet_search.rb | Loading commit data... | |
user.rb | Loading commit data... |