VSCode says my folder is not under source control when not launched with elevation.

[BrainSlugs83]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.70.1 (but it also happened in the previous version before upgrade)
• OS Version: Windows 10 - 19043

Steps to Reproduce:

1. Initialize a git repo from an elevated developer command prompt with git init
2. Open that folder from vscode, and click on the source control tab.
3. Observe that it does not recognize the folder as a git repo and instead offers you to initialize a new one. (I believe that for an existing repo this could cause serious issues and corrupt your repo!)
4. Open vscode with admin elevation, and open the same folder, observe that it now recognizes this folder as a git repo.

Expected Behavior:

Vscode should recognize the repo whether it is launched as an admin or not. -- If there is some permissions issue, it should display that as an error instead of offering to corrupt your repository for you!

[gjsjohnmurray]

See https://git-scm.com/docs/git-config/2.35.2#Documentation/git-config.txt-safedirectory

[gjsjohnmurray]

/duplicate of #150290

[vscodenpa]

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 similar existing issues. See also our issue reporting guidelines.

Happy Coding!

[BrainSlugs83]

/duplicate of #150290

@gjsjohnmurray -- I disagree; it is similar, but this bug is specific to elevation. -- The repo is ALREADY trusted, but I have to run vscode as an admin for it to notice!

VSCode should 1.) Not say there is no repo (so yes, same as #150290), but also 2.) it should not say it's not trusted (it IS trusted; it should instead tell me that I need to be elevated (and perhaps offer to relaunch in elevated mode).

[gjsjohnmurray]

/assign @lszomoru who can reopen the issue.

[lszomoru]

Closing as duplicate of #157159. This will be included in VS Code 1.74.