Gitlens as a web-extension shows console errors for uncomitted 'new' files are created in the workspace

[boltex]

Getting Uncaught (in promise) EntryNotFound (FileSystemError) for any new, uncommited files in the workspace. (see screenshot "new file.txt" example)

From the stack error traces in the console below the error itself, it seems gitlens tries to get 'stats' on those files wich do not exist yet on remote. (stats errors out if file doesnt exist, so a try/catch block should check if it exists first. Mabe i'm totally wrong as i'm pretty newb as a vscode extension developer)

• GitLens Version: 12.0.7
• Git Version: Run git --version Using as web extension, so no terminal to check git version
• vscode version 'about dialog' output: Version: 1.68.0 Commit: 4af164ea3a06f701fe3e89a2bcbb421d2026b68f Date: 2022-06-08T11:44:21.508Z Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.5005.115 Safari/537.36

Steps to Reproduce:

1. open url for vscode.dev on a pre-existing remote repository. (with gitlens installed obviously) such as https://vscode.dev/github/some-user/some-repo/tree/some-branch
2. create a simple hello.txt file with random content.
3. check console output.