Figure 1. A screenshot of the Create a Git Repository window showing the error message.
Figure 2. A screenshot of a newly generated solution, called Foo, where we are clicking the Create Git Repository button in the Git Changes window.
Figure 3. Using the Create a Git Repository window to push to a new remote.
Hello,
Please refer to the error message that I am being shown that is circled in Figure 1. This is an incorrect error message.
When I go to create a new Git repository on GitHub of the same name as one I’ve already created with Visual Studio (and then subsequently deleted from GitHub), and then go to create a new repository on GitHub of the same name, Visual Studio reports the error message that is shown above. However, Visual Studio is incorrectly displaying the error message; it’s a bug. There is no such repository on my GitHub, and I cannot find out how to get the error message to go away.
Restarting Visual Studio does not help. Clearing the cache on my browser does not help. Removing my GitHub account from Visual Studio and then re-adding it does not help. It’s as though there is a system file or Registry setting that tracks all the Git repos created with Visual Studio and it errors if that list contains the repo I am trying to re-create.
Steps to Reproduce
NOTE: These steps will only work on a solution that is, in and of itself, not already a member of a local GIt repository, nor is associated with a remote repository on GitHub. Furthermore, you should start off never having created a GitHub repository with the desired name. We will use Foo in this example, for the name of our new repository.
Open Visual Studio.
Create a new project using any template you choose.
Wait for the project to be generated.
Click the View menu, and then click Git Changes.
The Git Changes tool window appears (the GitHub Extension for Visual Studio has to be installed; this post assumes that that is the case).
Click the Create Git Repository button, as shown in Figure 2.
The Create a Git Repository window appears. Click the GitHub icon under Push to a New Remote as shown in Figure 3, and fill out the fields under the Initialize a Local Git Repository section.
Click Create and Push.
Visual Studio creates the new repository locally and then pushes it to GitHub.
Close Visual Studio and delete the newly-created solution from your hard drive.
In your browser, navigate to https://github.com and log in.
Click your profile icon, and then click Your Repositories.
The error in Figure 1 should now be (incorrectly) displayed.
I believe that there is a bug wherein Visual Studio or the GitHub Extension for Visual Studio does not do some checking to make sure that the repository Foo is still listed for the authenticated user.
Foo, where we are clicking the Create Git Repository button in the Git Changes window.Hello,
Please refer to the error message that I am being shown that is circled in Figure 1. This is an incorrect error message.
When I go to create a new Git repository on GitHub of the same name as one I’ve already created with Visual Studio (and then subsequently deleted from GitHub), and then go to create a new repository on GitHub of the same name, Visual Studio reports the error message that is shown above. However, Visual Studio is incorrectly displaying the error message; it’s a bug. There is no such repository on my GitHub, and I cannot find out how to get the error message to go away.
Restarting Visual Studio does not help. Clearing the cache on my browser does not help. Removing my GitHub account from Visual Studio and then re-adding it does not help. It’s as though there is a system file or Registry setting that tracks all the Git repos created with Visual Studio and it errors if that list contains the repo I am trying to re-create.
Steps to Reproduce
NOTE: These steps will only work on a solution that is, in and of itself, not already a member of a local GIt repository, nor is associated with a remote repository on GitHub. Furthermore, you should start off never having created a GitHub repository with the desired name. We will use
Fooin this example, for the name of our new repository.https://github.comand log in.Foorepository in the list.I believe that there is a bug wherein Visual Studio or the GitHub Extension for Visual Studio does not do some checking to make sure that the repository
Foois still listed for the authenticated user.