Description

This report is a follow-up to a negative review I wrote about GitLens. You may see my frustrated review and the response by Eric from GitKraken on the reviews page: https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens&ssr=false#review-details (I don't see any way to link directly to my review so if you are viewing this issue far in the future, my review may no longer exist at this link).

The problem I have is that GitLens does not respect my global VS Code telemetry settings after installation. I would expect for GitLens to either (a) comply with my settings for VS Code telemetry or (b) make it abundantly clear that VS Code telemetry settings are not being honored and direct me to manually choose whether or not I want telemetry to be enabled or disabled.

GitLens Version

13.4.0

VS Code Version

Version: 1.76.2
Commit: ee2b180d582a7f601fa6ecfdad8d9fd269ab1884
Date: 2023-03-14T17:57:21.103Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: 10.2.154.26-electron.0
OS: Linux x64 6.2.8-arch1-1
Sandboxed: No

Git Version

2.40.0

Logs, Screenshots, Screen Captures, etc

I have recorded my screen installing GitLens for you to see the exact behavior I experienced. While I did uninstall GitLens to re-install it in the recording (meaning the installation on the video is not technically a clean install on a system that has never had GitLens installed), I assure you the behavior in the video is the behavior I experienced when I did install GitLens for the first time.

Here is the video documenting my experience: https://www.youtube.com/watch?v=hlJdn11P2MQ