fatal: --unshallow on a complete repository does not make sense . Please check git output for more details

I did the following and this happened:

1. Checked out https://github.com/microsoft/vscode/pull/91615 for review via extension
2. While this was happening, I updated the branch with this button:

Output:

[Info] Looking for git repository
[Info] Git repository found, initializing review manager and pr tree view.
[Info] Review> Validate state in progress
[Info] Review> Validating state...
[Info] No remote with name 'origin' found. Please update your 'githubPullRequests.remotes' setting.
[Info] No remote with name 'ups' found. Please update your 'githubPullRequests.remotes' setting.
[Info] No GitHub remotes found
[Info] Review> Queuing additional validate state
[Info] Review> Validating state...
[Info] Review> no matching pull request metadata found for current branch tyriar/terminal_action2
[Info] Review> Queuing additional validate state
[Info] Review> Validating state...
[Info] No remote with name 'ups' found. Please update your 'githubPullRequests.remotes' setting.
[Info] Found GitHub remote
[Info] Review> no matching pull request metadata found for current branch tyriar/terminal_action2
[Info] Review> Queuing additional validate state
[Info] Review> Validating state...
[Info] No remote with name 'ups' found. Please update your 'githubPullRequests.remotes' setting.
[Info] Found GitHub remote
[Info] Review> no matching pull request metadata found for current branch master
[Info] Review> Queuing additional validate state
[Info] Review> Validating state...
[Info] No remote with name 'ups' found. Please update your 'githubPullRequests.remotes' setting.
[Info] Found GitHub remote
[Info] Review> no matching pull request metadata found for current branch master
[Info] Review> Queuing additional validate state
[Info] Review> Validating state...
[Info] No remote with name 'ups' found. Please update your 'githubPullRequests.remotes' setting.
[Info] Found GitHub remote
[Info] Review> no matching pull request metadata found for current branch master
[Info] Review> Queuing additional validate state
[Info] Review> Validating state...
[Info] No remote with name 'ups' found. Please update your 'githubPullRequests.remotes' setting.
[Info] Found GitHub remote
[Info] Review> no matching pull request metadata found for current branch master
[Info] Review> Queuing additional validate state
[Info] Review> Validating state...
[Info] No remote with name 'ups' found. Please update your 'githubPullRequests.remotes' setting.
[Info] Found GitHub remote
[Info] Review> no matching pull request metadata found for current branch master
[Info] Review> switch to Pull Request #91615 - start
[Info] Unshallowing failed: Failed to execute git {
  "exitCode": 1,
  "gitCommand": "pull",
  "stdout": "",
  "stderr": "fatal: --unshallow on a complete repository does not make sense\n"
}. Falling back to git pull
[Info] Review> checkout failed #{"message":"Failed to execute git","stdout":"","stderr":"fatal: --unshallow on a complete repository does not make sense\n","exitCode":1,"gitCommand":"pull"}
[Info] Review> Queuing additional validate state
[Info] Review> Validating state...
[Info] No remote with name 'ups' found. Please update your 'githubPullRequests.remotes' setting.
[Info] Found GitHub remote
[Info] Review> no matching pull request metadata found for current branch pr/jmbockhorst/91615
[Info] Review> Queuing additional validate state
[Info] Review> Validating state...
[Info] No remote with name 'ups' found. Please update your 'githubPullRequests.remotes' setting.
[Info] Found GitHub remote
[Info] Review> no matching pull request metadata found for current branch pr/jmbockhorst/91615

[Tyriar]

Let’s call this verified with the improved logging, I haven’t hit it since but if I do I can share the log.

[Tyriar]

I think they’re the same, can remember exactly what I did a month ago though.