Can't show blame when VSCode starts on branch without upstream

[benzittlau]

• GitLens Version: 8.2.1
• VSCode Version: 1.22.2
• OS Version: OS X 10.13.1

Steps to Reproduce:

1. Open VSCode while on a branch without an upstream
2. Toggle Line Blame Annotations

I'm encountering an issue where if VSCode launches while the project directory is on a branch that doesn't have an upstream, attempts to toggle file blame annotations will fail with the error:

No upstream configured for branch <branch name>

I attempted to enable "gitlens.outputLevel": "verbose", to record any output, but no output was visible in the output pane after adding that setting and restarting VSCode.

[benzittlau]

Just saw the same issue after:

1. Start VSCode on a branch with an upstream
2. Switch to a branch without an upstream
3. Open a new file
4. Toggle Line Blame Annotations

It appears that once it gets into this state it stays broken (if I switch back to master with an upstream I continue to get the error trying to toggle the annotations on the newly opened file).

[eamodio]

I think this is related to a casing issue in the git error messages. I've switched to use case insensitive matching and hopefully that will resolve this.

[benzittlau]

@eamodio You just made my day! Confirmed locally that with version 8.2.3 I am no longer seeing this issue. Thanks for your active support of this project!

[eamodio]

Awesome glad to hear it is actually fixed! 😄

[ryenus]

I still have this issue on with 8.3.3 :-(

[ryenus]

Here the error I got is.

> git rev-parse --symbolic-full-name my_branch@{u}
fatal: upstream branch 'refs/heads/my_branch' not stored as a remote-tracking branch

Git version 2.17.1

[ryenus]

FYI, I've created pull request #390.