Git being too generous with modal dialogs

[jrieken]

• have vs code open
• be in a browser for a while
• go back to VS Code, press the git status bar icon to sync incoming changes
• you will almost certainly get a modal dialog "informing" you about failure

suggestions

• suggestion: don't fail so often
• suggestion: don't block my work with not so informative modal dialogs

[jrieken]

> git rev-parse master
> git rev-parse --symbolic-full-name master@{u}
> git rev-list --left-right master...refs/remotes/origin/master
> git for-each-ref --format %(refname) %(objectname) --sort -committerdate
> git remote --verbose
> git status -z -u
> git symbolic-ref --short HEAD
> git rev-parse master
> git rev-parse --symbolic-full-name master@{u}
> git rev-list --left-right master...refs/remotes/origin/master
> git for-each-ref --format %(refname) %(objectname) --sort -committerdate
> git remote --verbose
> git fetch
> git pull --tags origin master
From github.com:Microsoft/vscode
   d1a9e7f2b2..a550394f34  master     -> origin/master
> git status -z -u
From github.com:Microsoft/vscode
 * branch                  master     -> FETCH_HEAD
error: cannot lock ref 'refs/remotes/origin/master': is at a550394f34888639ff7bb3d5b6742babe46d59f5 but expected d1a9e7f2b2c5211804c99d4f4c16c9d00350f84f
 ! d1a9e7f2b2..a550394f34  master     -> origin/master  (unable to update local ref)
> git symbolic-ref --short HEAD
> git rev-parse master
> git rev-parse --symbolic-full-name master@{u}
> git rev-list --left-right master...refs/remotes/origin/master
> git for-each-ref --format %(refname) %(objectname) --sort -committerdate
> git remote --verbose

[joaomoreno]

/duplicate #47141

Moving it for September.

[vscodebot]

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.

Happy Coding!