Skip to content

Handle project logo for private project

Summary

When a project in your "FREQUENTLY VISITED PROJECTS" list is private and requires login the logo is also unavailable before logging in.

Possible fixes:

  1. Handle a broken logo link correctly
  2. When a project requires further auth, replace logo with a generic "private logo"

Steps to reproduce

Example Project

What is the current bug behavior?

What is the expected correct behavior?

Relevant logs and/or screenshots

before login after login
Screenshot_2023-04-20_at_10.30.15 Screenshot_2023-04-20_at_10.34.59

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of: sudo gitlab-rake gitlab:check SANITIZE=true)

(For installations from source run and paste the output of: sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)

(we will only investigate if the tests are passing)

Possible fixes

Edited by James Rushford