Error внешний репозиторий origin уже существует

This article discusses how to resolve the issue git fatal: remote origin already exists error during the push or add commands.

Fix git fatal: remote origin already exists error on push

You must run the ‘git init’ command to enable git for any application or folder/directory.

Once git is initialized, we must either create a new repository or clone an existing repository to map this to the existing directory.

if this directory is created in the nested folder of any git repository, the git command throws git fatal: remote origin already exists error.

What does its origin mean?

This error comes during multiple use cases.

• created a local nested folder app, It is a child folder of a local git repository, these folders map to the new remote repository.

B:blogjswork>git remote add origin https://github.com/intkiran/react-auth0-login.git
fatal: remote origin already exists.

An error would

fatal: remote origin already exists.

From the above code, It creates an origin local name and adds it to an existing repository.

In any local repository, How do you know the remote repository url?
using the -v option gives the local name with a remote url as described following

And the output is

origin  https://github.com/intkiran/react-auth0-login.git (fetch)
origin  https://github.com/intkiran/react-auth0-login.git (push)

It gives the remote repository url mapped with the local name i.e origin.

Origin is the local name for the remote repository given by default.

This error occurs after adding a new url to the existing origin.

This post covers the solution for the following errors in the git command

• fatal: No such remote:
• Remote origin already exists on ‘git push’ to a new repository

There are many ways we can fix this.

Remove the original name from the given existing repository

First, delete the local name origin for a given remote repository using the following command.

next, add the original name to the new remote repository

git remote add origin remote-repo-url

set-url Change origin name from the given existing git repository

git remote set-url neworigin remote-repo-url

if remote-repo-url does not exist, it gives an error fatal: No such remote:.

Replace current origin with new url in Git

below set the new url for the local name origin.

git remote set-url origin remote-repo-url

rename existing origin name in Git

The last approach is to rename the existing origin to the new name

git remote rename origin neworigin

Finally, Verify the name mapped to the URLs using the below command.

wrap

There are many ways we can fix these errors with the above solutions.

Ключевое слово «origin» обычно используется для описания центрального источника (ресурса на сервере) репозитория Git. Если Вы попытаетесь добавить удаленный сервер (remote), так называемый «origin» к репозиторию, в котором описание origin уже существует, то получите ошибку «fatal: remote origin already exists». В этой статье (перевод [1]) мы обсудим подобный случай проблемы «fatal: remote origin already exists» и способ её решения.

Ошибка Git «fatal: remote origin already exists» показывает вам, что Вы пытаетесь создать remote с именем «origin», когда remote с таким именем уже существует (был прописан ранее). Это ошибка — общий случай, когда вы забыли, что уже настроили ссылку на remote репозиторий, и снова выполняете инструкции по установке. Также эту ошибку можно увидеть, если делается попытка поменять URL «origin» remote-репозитория командой git remote add.

Чтобы исправить эту ошибку, нужно сначала проверить, связан ли в настоящий момент remote с ключевым словом «origin», и что у него корректный URL. Вы можете сделать это командой git remote -v:

m:asmradiopager>git remote -v
origin  https://github.com/microsindotnet/git (fetch)
origin  https://github.com/microsindotnet/git (push)

Если «origin» URL не соответствует URL Вашего remote-репозитория, к которому Вы хотите обратиться, то можно поменять remote URL. Альтернативно можно удалить remote, и заново установить remote URL с именем «origin».

Пример проблемной ситуации. У нас есть некий репозиторий с именем «git», и мы хотим поменять его текущий origin:

https://github.com/microsindotnet/git

На новый origin:

https://github.com/microsindotnet/gitnew

Чтобы сделать это, мы используем команду git remote add command, который добавляет новый remote к репозиторию:

git remote add origin https://github.com/microsindotnet/gitnew

Но эта команда вернула ошибку:

fatal: remote origin already exists.

Этим сообщением git говорит нам, что remote origin уже существует.

Способ решения проблемы. Мы не можем добавить новый remote, используя имя, которое уже используется, даже если мы указываем для remote новый URL. В этом случае мы попытались создать новый remote с именем «origin», когда remote с таким именем уже существует. Чтобы исправить эту ошибку, мы должны удалить существующий remote, который называется «origin», и добавить новый, либо должны поменять URL существующего remote.

Чтобы удалить существующий remote и добавить новый, мы можем установить новый URL для нашего remote:

git remote set-url origin https://github.com/microsindotnet/gitnew

Это предпочтительный метод, потому что мы можем в одной команде поменять URL, связанный с нашим remote. Не понадобится уделить старый origin и создавать новый, потому что существует команда set-url.

Альтернативно мы можем удалить наш remote «origin», и после этого создать новый, с новым URL:

git remote rm origin
git remote add origin https://github.com/microsindotnet/gitnew

Этот метод использует 2 команды вместо одной.

[Ссылки]

1. Git fatal: remote origin already exists Solution site:careerkarma.com.
2. git: быстрый старт.

Error внешний репозиторий origin уже существует

Ключевое слово «origin» обычно используется для описания центрального источника (ресурса на сервере) репозитория Git. Если Вы попытаетесь добавить удаленный сервер (remote), так называемый «origin» к репозиторию, в котором описание origin уже существует, то получите ошибку «fatal: remote origin already exists». В этой статье (перевод [1]) мы обсудим подобный случай проблемы «fatal: remote origin already exists» и способ её решения.

Ошибка Git «fatal: remote origin already exists» показывает вам, что Вы пытаетесь создать remote с именем «origin», когда remote с таким именем уже существует (был прописан ранее). Это ошибка — общий случай, когда вы забыли, что уже настроили ссылку на remote репозиторий, и снова выполняете инструкции по установке. Также эту ошибку можно увидеть, если делается попытка поменять URL «origin» remote-репозитория командой git remote add.

Чтобы исправить эту ошибку, нужно сначала проверить, связан ли в настоящий момент remote с ключевым словом «origin», и что у него корректный URL. Вы можете сделать это командой git remote -v:

Если «origin» URL не соответствует URL Вашего remote-репозитория, к которому Вы хотите обратиться, то можно поменять remote URL. Альтернативно можно удалить remote, и заново установить remote URL с именем «origin».

Пример проблемной ситуации. У нас есть некий репозиторий с именем «git», и мы хотим поменять его текущий origin:

На новый origin:

Чтобы сделать это, мы используем команду git remote add command, который добавляет новый remote к репозиторию:

Но эта команда вернула ошибку:

Этим сообщением git говорит нам, что remote origin уже существует.

Способ решения проблемы. Мы не можем добавить новый remote, используя имя, которое уже используется, даже если мы указываем для remote новый URL. В этом случае мы попытались создать новый remote с именем «origin», когда remote с таким именем уже существует. Чтобы исправить эту ошибку, мы должны удалить существующий remote, который называется «origin», и добавить новый, либо должны поменять URL существующего remote.

Чтобы удалить существующий remote и добавить новый, мы можем установить новый URL для нашего remote:

Это предпочтительный метод, потому что мы можем в одной команде поменять URL, связанный с нашим remote. Не понадобится уделить старый origin и создавать новый, потому что существует команда set-url.

Альтернативно мы можем удалить наш remote «origin», и после этого создать новый, с новым URL:

Этот метод использует 2 команды вместо одной.

Источник

Git — fatal: remote origin already exists

I can not create origin remotely with remote command:

To solve the error, I have tried this:

It is not uploading the files from my local repository to the remote:

Does each repository have its own origin?

Solution: I was using the Powershell that came with Github or Git Shell as it is also called to do my tutorial, once I switched to Git Bash it worked fine.

4 Answers 4

That will replace the current origin with a new one.

git remote rm origin

git remote add origin https://yourLink

I had a similar issue but I got it resolved using:

In order to use git push, you must specify final destination follorwed by local_branch ( in my own case, it is master for the local branch and main for the remote branch). They could however be the same. As in:

It’s quite strange as to why your origin doesn’t have a value. Typically, it should look like this:

Your origin doesn’t have the url associate with it. It’s actually name value pair. So when you say «git push origin master», Git substitues the value of origin. In my case, it would be «/mnt/temp.git».

Now what can you do ?

1) Clone the repository in another directory.

2) run » git remote -v » and get the value of origin

4) So come back to your working directory, and run » git remote add origin2 https://github.com/LongKnight/git-basics.git «

5) Run » git remote remove origin «

6) Now run » git remote rename origin2 origin «

7) Check what’s the value of origin now with «git remote -v»

It should be correctly set now. If so, run » git push «

Источник

Fix git fatal: remote origin already exists error on push

This article discusses how to resolve the issue git fatal: remote origin already exists error during the push or add commands.

Fix git fatal: remote origin already exists error on push

You must run the ‘git init’ command to enable git for any application or folder/directory.

Once git is initialized, we must either create a new repository or clone an existing repository to map this to the existing directory.

if this directory is created in the nested folder of any git repository, the git command throws git fatal: remote origin already exists error.

What does its origin mean?

This error comes during multiple use cases.

• created a local nested folder app, It is a child folder of a local git repository, these folders map to the new remote repository.

From the above code, It creates an origin local name and adds it to an existing repository.

In any local repository, How do you know the remote repository url? using the -v option gives the local name with a remote url as described following

And the output is

It gives the remote repository url mapped with the local name i.e origin.

Origin is the local name for the remote repository given by default.

This error occurs after adding a new url to the existing origin.

This post covers the solution for the following errors in the git command

• fatal: No such remote:
• Remote origin already exists on ‘git push’ to a new repository

There are many ways we can fix this.

Remove the original name from the given existing repository

First, delete the local name origin for a given remote repository using the following command.

next, add the original name to the new remote repository

set-url Change origin name from the given existing git repository

if remote-repo-url does not exist, it gives an error fatal: No such remote: .

Replace current origin with new url in Git

below set the new url for the local name origin.

rename existing origin name in Git

The last approach is to rename the existing origin to the new name

Finally, Verify the name mapped to the URLs using the below command.

There are many ways we can fix these errors with the above solutions.

Источник

GitHub «fatal: remote origin already exists»

I am trying to follow along Michael Hartl’s Rails tutorial but I’ve run across an error.

I signed up on Github and issued a new SSH key and made a new repository. But when I enter the next line into the terminal I get the following error:

Just wondered if anybody else has run across this problem?

25 Answers 25

TL;DR you should just update the existing remote:

Long version:

As the error message indicates, there is already a remote configured with the same name. So you can either add the new remote with a different name or update the existing one if you don’t need it:

To add a new remote, called for example github instead of origin (which obviously already exists in your system), do the following:

Remember though, everywhere in the tutorial you see «origin» you should replace it with «github». For example $ git push origin master should now be $ git push github master .

However, if you want to see what that origin which already exists is, you can do a $ git remote -v . If you think this is there by some error, you can update it like so:

and voila! Worked for me!

You can see what remote repositories you are configured to connect to via

That will return a list in this format:

That might help you figure out what the original ‘origin’ pointed to.

If you want to keep the remote connection that you see with the -v, but still want to follow the Rails tutorial without having to remember ‘github’ (or some other name) for your tutorial’s repo, you can rename your other repository with the command:

You should then be able to resume your tutorial.

For those of you running into the ever so common error «fatal: remote origin already exists.», or when trying to remove origin and you get «error: could not remove config section remote.origin», what you need to do is to set the origin manually.

Git for Windows PowerShell (and GitHub for Windows’ app) has a problem with this.

I ran into this, like I do so often, again when setting up my octopress. So, here’s how I got it working.

First, check your remotes:

You’ll first note that my origin has no url. Any attempt to remove it, rename it, etc all fails.

So, change the url manually:

Then you can confirm it worked by running git remote -v again:

This has fixed dozens of git repos I’ve had issues with, GitHub, BitBucket GitLab, etc.

In the special case that you are creating a new repository starting from an old repository that you used as template (Don’t do this if this is not your case). Completely erase the git files of the old repository so you can start a new one:

And then restart a new git repository as usual:

update the origin if it exist already using this command

If you need to check which remote repos you have connected with your local repos, theres a cmd:

Now if you want to remove the remote repo (say, origin) then what you can do is:

I am facing issue in Bitbucket while push the code in remote

Follow below steps:

Step-1: Update the existing remote

Step-2: You can use this command to force changes to the server with the local repository. Remote repo code will be replaced with your local repo code.

-f Usually, the command refuses to update a remote ref that is not an ancestor of the local ref used to overwrite it.

That error message indicates that you already have a remote in your git directory. If you are satisfied with that remote, your can push your code. If not or if you can’t push just:

The concept of remote is simply the URL of your remote repository.

The origin is an alias pointing to that URL. So instead of writing the whole URL every single time we want to push something to our repository, we just use this alias and run:

git push -u origin master

Telling to git to push our code from our local master branch to the remote origin repository.

Whenever we clone a repository, git creates this alias for us by default. Also whenever we create a new repository, we just create it our self.

Whatever the case it is, we can always change this name to anything we like, running this:

Since it is stored on the client side of the git application (on our machine) changing it will not affect anything in our development process, neither at our remote repository. Remember, it is only a name pointing to an address.

The only thing that changes here by renaming the alias, is that we have to declare this new name every time we push something to our repository.

git push -u my-remote-alias master

Obviously a single name can not point to two different addresses. That’s why you get this error message. There is already an alias named origin at your local machine. To see how many aliases you have and what are they, you can initiate this command:

This will show you all the aliases you have plus the corresponding URLs.

You can remove them as well if you like running this:

Источник

Remote origin already exists on ‘git push’ to a new repository

I have my project on GitHub at some location, git@github.com:myname/oldrep.git .

Now I want to push all my code to a new repository at some other location, git@github.com:newname/newrep.git .

I used the command:

but I am receiving this:

fatal: remote origin already exists.

22 Answers 22

You are getting this error because «origin» is not available. «origin» is a convention not part of the command. «origin» is the local name of the remote repository.

For example you could also write:

To remove a remote repository you enter:

Again «origin» is the name of the remote repository if you want to remove the «upstream» remote:

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:

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:

METHOD1->

Since origin already exist remove it.

METHOD2->

One can also change existing remote repository URL by ->git remote set-url

If you’re updating to use HTTPS

If you’re updating to use SSH

If trying to update a remote that doesn’t exist you will receive a error. So be careful of that.

METHOD3->

Use the git remote rename command to rename an existing remote. An existing remote name, for example, origin.

To verify remote’s new name->

If new to Git try this tutorial->

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

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

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

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).

I had 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 the task menu. This will open a power shell including Git commands.
3. In the shell, switch to your old repository, e.g. cd C:pathtooldrepository .
4. Show the 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:

If it’s not connected, it might show origin only.

Now remove the remote repository from the local repository by using

Check again with git remote -v , as in step 4. It should show origin only, instead of the fetch and push path.

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 as well.

Источник

What is the ‘fatal: remote origin already exists’ error?

fatal: remote origin already exists is a common Git error that occurs when you clone a repository from GitHub, or an external remote repository, into your local machine and then try to update the pointing origin URL to your own repository.

In the context of Kubernetes, the error can occur when you configure orchestrations to include Git repositories. For example, by using: git remote add origin [url].gits

fatal: remote origin already exists is caused by the cloned repository already having a URL configured. Specifically, a URL that leads to the original profile where the repository source is.

What is a remote origin in Git?

remote origin, as the name implies, is the place where code is stored remotely. It is the centralized server or zone where everyone pushes code to and pulls code from.

Remote repositories are versions of your project hosted on Git-compatible platforms such as GitHub, Bitbucket, GitLab, and Assembla. origin is the standard and generic handle that is used to associate the host site’s URL.

For example, you can have an alternative remote URL called dev, which then becomes the handle for a separate repository but for the same code.

When you run git remote -v, you will get a list of handles and associated URLs. So if you have different handlers for the same remote, the console output could look something like this:

D:GitHubgit remote -v
origin  https://github.com/prod_repo/projectx.git (fetch)
origin  https://github.com/prod_repo/projectx.git (push)
dev     https://github.com/dev_repo/projectx.git (fetch)
dev     https://github.com/dev_repo/projectx.git (push)  

This means that you can run the following command: git push dev master

The changes made will get pushed up to the master branch at the URL associated with dev and not origin.

Resolving ‘fatal: remote origin already exists’

For most development environments, origin is the default handler used. Here are 3 ways to resolve fatal: remote origin already exists.

1. Remove the Existing Remote

remote refers to the hosted repository. origin is the pointer to where that remote is. Most of the time, origin is the only pointer there is on a local repository.

If you want to change the pointing URL attached to origin, you can remove the existing origin and then add it back in again with the correct URL.
To remove your handler, use the remove command on remote, followed by the handler name – which, in our case, is origin.
Here is an example: git remote remove origin

To check that handler is deleted properly, run the following: git remote -v

You will either get an empty list, or you will get a list of remote handlers that are currently attached to the project with origin removed from the list.
Now you can run git remote add origin [url].git without encountering the fatal: remote origin already exists error.

2. Update the Existing Remote’s URL

You are not always required to remove the origin handler from remote. An alternative way to solve fatal: remote origin already exists is to update the handler’s pointing URL.

To do this, you can use the set-url command, followed by the handler name (which is origin in our case) and the new URL.

Here is the syntax for updating an existing origin URL: git remote set-url origin [new-url]

Once this is completed, you can now push and pull code from the newly configured Git repository location.

3. Rename the Existing Remote

Alternatively, you can rename origin to something else. This means that instead of deleting the handler’s pointing URL to make room for the new one, you can rename it and keep the original details.

To do this, use the rename command on: remote.

For example, if you want to rename origin to dev, you can use the following command: git remote rename origin dev

Now when you run git remote -v, you will get dev as the handler instead of origin.

D:GitHub[some-repo]git remote -v
dev     https://github.com/some_repo/projectx.git (fetch)
dev     https://github.com/some_repo/projectx.git (push)  

This will give you room to add a new origin to the list of attached handlers. So when you run git remote add origin [url].git, you will no longer get the fatal: remote origin already exists error prompt.

How to prevent ‘fatal: remote origin already exists’

To prevent fatal: remote origin already exists error from occurring, you can check if the origin handler already exists. If it does not, running the git add remote origin command should not produce this issue.

The most important thing to note here is that origin is only a handler’s short name. It is a reference to the URL, which is where the actual remote repository is hosted.

The handler origin just happens to be the standardized default. This is what makes fatal: remote origin already exists so common. The error itself can occur against any handler, provided that it has the same placeholder name.

To check if origin even exists, run git remote -v to get a list of current remote handlers and the associated URLs.

If origin exists, you can do one of the following:

• remove origin from the remote list via remove command, like so: git remote remove origin
• update origin pointing URL with set-url, like so:git remote set-url origin [new-url]
• rename the existing origin handler to something else via rename command: git remote rename origin [new-name]

K8s troubleshooting with Komodor

We hope that the guide above helps you better understand the troubleshooting steps you need to take in order to fix the fatal: remote origin already exists error.

Keep in mind that this is just one of many Git errors that can pop up in your k8s logs and cause the system to fail. Due to the complex and distributed nature of k8s,
the search for the root cause of each such failure can be stressful, disorienting and time-consuming.

This is why we created Komodor, which acts as a single source of truth (SSOT) to streamline and shorten your k8s troubleshooting processes. Among other features, it offers:

• Change intelligence: Every issue is a result of a change. Within seconds we can help you understand exactly who did what and when.
• In-depth visibility: A complete activity timeline, showing all code and config changes, deployments, alerts, code diffs, pod logs and etc. All within one pane of glass with easy drill-down options.
• Insights into service dependencies: An easy way to understand cross-service changes and visualize their ripple effects across your entire system.
• Seamless notifications: Direct integration with your existing communication channels (e.g., Slack) so you’ll have all the information you need, when you need it.