Remote 'origin' already exists when it does not

Does this issue occur when all extensions are disabled?: n/a Needs Git extension

• VS Code Version: 1.69.0
• OS Version: Windows 11 - Version 10.0.22000 Build 22000

Steps to Reproduce:

1. Initalise a new repository
2. Open git repo in sourcecode panel
3. Remote -> Add Remote
4. use origin as the remote name
5. Error Remote ‘origin’ already exists
6. Confirm origin doesn’t exist git remote get-url --all origin -> error: No such remote 'origin'
7. Use terminal to add remote git remote add origin <url>

You can then remove the origin remote using the Remote -> Remove Remote, and then try adding it using the UI and it still fails.

[flipkickmedia]

The worst part about that was it opening nano…vim till I die.

Ok so yes there is config defined, but this config is required to prune from origin when I fetch. This is another issue with VSCode, it ignores this config and doesn’t prune but that aside (Ill open another ticket for that) this config is needed.

I’d suggest reworking the handling of remotes, and only when there is a URL should you complain about it existing.

git config --system -e
<Returns nothing>

git config --global -e

[user]
        name = Tom Shaw
        email = [e-mail]
[credential]
        helper = manager-core
[pull]
        rebase = false
[remote "origin"]
        prune = true
[core]
        fileMode = true
[url "ssh://[e-mail]"]
        insteadOf = https://git.flipkick.media

[lszomoru]

@flipkickmedia, thanks for the running the tests and for providing the additional information. Based on the provided data, it does look like VS Code correctly removes the “remote” section from the repository’s git config file. Having said that I just checked and if we cannot find any remotes in the repository’s git config file, we will always fallback to the output of git remote -v.

I believe that what we have to understand is why git remote -v returns a remote even though all remotes have been deleted. The only think that I can think of is that somehow either the system or the global git config has a “origin” remote defined and that is what is being returns by the git remote -v command. Could you please run these commands and see if the config files contain the “origin” remote:

• git config --system -e
• git config --global -e