Eric Amodio

I think a progress bar would be a good addition. FWIW, we added a ProgressIndicator webcomponent in GitLens using the VS Code styles: https://github.com/gitkraken/vscode-gitlens/blob/d65bc6e2722ee9f9d94633942ee1fb837cfb2e12/src/webviews/apps/shared/components/progress.ts#L1

That error in the logs is completely benign and not related to the inline blame in any way. Can you please enable debug logging by running the _GitLens: Enable Debug...

Interesting idea, unfortunately GitLens can't add anything to the source control view as you'd mocked up there (the VS Code APIs don't allow for anything like that). But there are...

I think the issue is that you need to fill out more properties in your custom remote: ``` "gitlens.remotes": [ { "domain": "gitlab.example.com", "type": "GitLab", "urls": { "repository": "https://git.corporate-url.com:8000/${repo}", "branches":...

@bitfield if you set it up with the structure I provided does it work? Depending on that -- there is either a bug or documentation issues

All the `file*` properties contribute to different aspects of how GitLens builds file urls. - `file` is the base url for a file on HEAD (i.e. not targeting a specific...

Yes, but then other features like `Open Commit on Remote`, `Open Branch on Remote`, etc would be broken. You will also need to set `fileLine` & `fileRange` to match what...

Hey all sorry for this issues here, and in the latest release (15.1 or the current pre-release) we've added some settings to try to understand how to optimize our queries...

@ibqn even in 15.0 you should only have seen the error once at VS Code open, and at most a couple more times in 30m intervals before we turned off...

@rhaschke What warning are you seeing? In the latest version there shouldn't be any warning/notification outside of the a ⚠️ icon next to the Launchpad 🚀 icon