Remote origin already exists on 'git push' to a new repository

The previous solutions seem to ignore origin, and they only suggest to use another name. When you just want to use git push origin, keep reading.

The problem appears because a wrong order of Git configuration is followed. You might have already added a 'git origin' to your .git configuration.

You can change the remote origin in your Git configuration with the following line:

git remote set-url origin git@github.com:username/projectname.git

This command sets a new URL for the Git repository you want to push to. Important is to fill in your own username and projectname

If you have mistakenly named the local name as "origin", you may remove it with the following:

git remote rm origin

You can simply edit your configuration file in a text editor.

In the ~/.gitconfig you need to put in something like the following:

[user]
        name  = Uzumaki Naruto
        email = myname@example.com

[github]
        user = myname
        token = ff44ff8da195fee471eed6543b53f1ff

In the oldrep/.git/config file (in the configuration file of your repository):

[remote "github"]
        url = git@github.com:myname/oldrep.git
        push  = +refs/heads/*:refs/heads/*
        push  = +refs/tags/*:refs/tags/*

If there is a remote section in your repository's configuration file, and the URL matches, you need only to add push configuration. If you use a public URL for fetching, you can put in the URL for pushing as 'pushurl' (warning: this requires the just-released Git version 1.6.4).

You don't have to remove your existing "origin" remote, just use a name other than "origin" for your remote add, e.g.

git remote add github git@github.com:myname/oldrep.git

I got the same issue, and here is how I fixed it after doing some research:

1. Download GitHub for Windows or use something similar, which includes a shell
2. Open the Git Shell from task menu. This will open a power shell including Git commands.
3. In the shell, switch to your old repository, e.g. cd C:\path\to\old\repository

4. Show status of the old repository

   • Type git remote -v to get the remote path for fetch and push remote. If your local repository is connected to a remote, it will show something like this:

     origin https://user@bitbucket.org/team-or-user-name/myproject.git (fetch) origin https://user@bitbucket.org/team-or-user-name/myproject.git (push)

   • If it's not connected, it might show origin only.

5. Now remove the remote repository from local repository by using

   git remote rm origin
   

6. Check again with step 4. It should show origin only, instead of the fetch and push path.

7. Now that your old remote repository is disconnected, you can add the new remote repository. Use the following to connect to your new repository.

Note: In case you are using Bitbucket, you would create a project on Bitbucket first. After creation, Bitbucket will display all required Git commands to push your repository to remote, which look similar to the next code snippet. However, this works for other repositories, too.

cd /path/to/my/repo # If haven't done yet
git remote add mynewrepo https://user@bitbucket.org/team-or-user-name/myproject.git
git push -u mynewrepo master # To push changes for the first time

That's it.

You could also change the repository name you wish to push to in the REPOHOME/.git/config file

(where REPOHOME is the path to your local clone of the repository).

I had the same problem when I first set up using Bitbucket.

My problem was that I needed to change the word origin for something self-defined. I used the name of the application. So:

git remote add AppName https://someone@bitbucket.org/somewhere/something.git

You should change the name of the remote repository to something else.

git remote add origin git@github.com:myname/oldrep.git

to

git remote add neworigin git@github.com:myname/oldrep.git

I think this should work.

Yes, these are for repository init and adding a new remote. Just with a change of name.