Adds custom avatar

[tmkx]

Description

Allow custom avatar url rule, backward compatible.

 "gitlens.remotes": [
   {
     "domain": "gitlab.intranet.com",
     "type": "Custom",
     "name": "Company",
     "protocol": "https",
     "urls": {
       "repository": "https://gitlab.intranet.com/${repo}",
       "branches": "https://gitlab.intranet.com/${repo}/branches",
       "branch": "https://gitlab.intranet.com/${repo}/commits/${branch}",
       "commit": "https://gitlab.intranet.com/${repo}/commit/${id}",
       "file": "https://gitlab.intranet.com/${repo}?path=${file}${line}",
       "fileInBranch": "https://gitlab.intranet.com/${repo}/blob/${branch}/${file}${line}",
       "fileInCommit": "https://gitlab.intranet.com/${repo}/blob/${id}/${file}${line}",
       "fileLine": "#L${line}",
       "fileRange": "#L${start}-L${end}",
+      "avatar": "https://avatar.intranet.com/employee?username=${name}&size=${size}"
     }
   }
 ]

close #302
close #1036

Checklist

• I have followed the guidelines in the Contributing document
• My changes follow the coding style of this project
• My changes build without any errors or warnings
• My changes have been formatted and linted
• My changes include any required corresponding changes to the documentation
• My changes have been rebased and squashed to the minimal number (typically 1) of relevant commits
• My changes have a descriptive commit message with a short title, including a Fixes $XXX - or Closes #XXX - prefix to auto-close the issue that your PR addresses

[xiaoas]

seems very promising. The MR will also give a more general solution to #281.

However the way custom avatar uri was provided was as a member of the Account class, bond to a commit. Might need further review from the repo maintainer.

[manc-lx]

@tmkx , Why this PR is still pending? My organization is using azure devops, does this PR work on azure devops?

[tmkx]

@tmkx , Why this PR is still pending? My organization is using azure devops, does this PR work on azure devops?

It's fully customizable, as well as can be used in azure.

[nunnsy]

Is anyone still actively working on this?

[nunnsy]

thanks @tmkx! @axosoft-ramint @eamodio just wondering if there's anything that needs to be done here before a review? cheers

[John-Dean]

Is there any movement on this? I found issue #281 which is marked as closed but it seems to not function/there is no setting(?). I can't reply on the issue as it's marked as closed with no comments.

This PR seems like a fix for it and it's been sitting for a while.

Echoing what @nunnsy said; @tmkx is this ready for review?

[tmkx]

@tmkx is this ready for review?

Yes

[baranwang]

When the PR will be merged into the main branch? @eamodio @d13

[latel]

When the PR will be merged into the main branch?

[baranwang]

ping @eamodio @d13 @axosoft-ramint