Thanks — appreciate the kind words.

This request is very similar to #281 and unfortunately my response is the same (at least at this point).

See #281 (comment)

Sounds like a lot of upfront processing work, that is very GitHub specific. I normally try to stay away from features that will only work with 1 provider/host, since I want GitLens to have a broader reach and no favorites 😄
Given the challenges here and the value of the feature imo -- it isn't worth the investment (for me). But if the community wants to submit a PR (start with a spec first please) I'm open.

Okay :), I might have some time to look into it.

You don't need to run vscode from source, just GitLens. Just clone the repo, run npm install and then you should be able to hit F5 in vscode.

FYI, just so you know for me to accept a PR around this, it can't negatively affect performance (startup or otherwise) and it can't interfere with offline support.

Also this should be a somewhat generic solution that can be used for GitHub and other providers that have avatar support.

Jeah I was looking at the remotes folder and can use the url of the repo to deduct what kind of repo someone has. Private repos like gitlab, mostly still have the word GitLab in it. Github is more straight forward.

[remote "origin"]
	url = gitlab@gitlab.privatenetwork.net:nicerepo/reporepo.git
	fetch = +refs/heads/*:refs/remotes/origin/*

FYI, GitLens already parses remotes -- which you can get access too by using Container.git.getRemotes(<repopath>) and the remotes will get automatically matched to a known provider if possible (those are the files in the `/git/remotes' folder.

This should be pretty easy to implement now as the infrastructure is there for GitHub, and should be copy-able for GitLab

I'm not sure if this is the correct issue, but currently GitLens+ doesn't seem to pull my correct GitLab avatar: https://gitlab.com/Nezteb

Even if it did fallback to Gravatar, it should be using:

Instead I get:

I've verified that the commits have my correct email associated with them. The other randomized avatar is a coworker's, but his GitLab avatar is not set, so for him this is correct behavior.

Another odd thing is that despite having the avatar style set to robohash, the extension is still using identicon:

If there are any good ideas for debugging steps, let me know! I don't have any other git-related plugins installed, which is the only reason I'm assuming it's vscode-gitlens. 😅