Skip to content

[Feature]: Pick up project icons more reliably outside React apps #4304

Description

@levelorbit

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I am describing a concrete problem or use case, not just a vague idea.

Area

apps/server

Problem or use case

Project icons in the Sidebar V2 chip row often fall back to the generic folder glyph. From my observation this works well for React projects and poorly for others.

I'd like the app to pick up project icons more reliably across more kinds of repos.

Version: 0.0.29-nightly.20260722.878 (9a0a07167f06)

Proposed solution

Improve icon discovery so non-React projects get icons more often.

Why this matters

The project row is easier to scan when each project has a distinct mark. Right now mixed lists look incomplete.

Smallest useful scope

Make discovery work better for common non-React project layouts.

Alternatives considered

No response

Risks or tradeoffs

No response

Examples or references

No response

Contribution

  • I would be open to helping implement this.

Activity

  1. added
    enhancementRequested improvement or new capability.
    needs-triageIssue needs maintainer review and initial categorization.
    on Jul 22, 2026
  2. juliusmarminge commented on Jul 22, 2026

    @juliusmarminge
    Member

    where do you have the favicon in your proejct?

  3. levelorbit commented on Jul 23, 2026

    @levelorbit
    Author

    Usually static/ or public/ (sometimes static/icons/). React and Vue defaults resolve fine for me, but other frameworks’ layouts don’t.

  4. dain commented on Aug 8, 2026

    @dain

    How about pulling the GitHub owner.avatar_url or GitLab avatar_url as a fallback? Since T3 already resolves the Git remote and source-control provider, it has the information needed for the API request.

    Concrete example: https://api.github.com/repos/trinodb/trino returns owner.avatar_url as https://avatars.githubusercontent.com/u/34147222?v=4.

  5. locked and limited conversation to collaborators on Aug 15, 2026
  6. converted this issue into a discussion #6799 on Aug 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementRequested improvement or new capability.needs-triageIssue needs maintainer review and initial categorization.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions