Git how to change origin

Working with Remotes

To be able to collaborate on any Git project, you need to know how to manage your remote repositories. Remote repositories are versions of your project that are hosted on the Internet or network somewhere. You can have several of them, each of which generally is either read-only or read/write for you. Collaborating with others involves managing these remote repositories and pushing and pulling data to and from them when you need to share work. Managing remote repositories includes knowing how to add remote repositories, remove remotes that are no longer valid, manage various remote branches and define them as being tracked or not, and more. In this section, we’ll cover some of these remote-management skills.

It is entirely possible that you can be working with a “remote” repository that is, in fact, on the same host you are. The word “remote” does not necessarily imply that the repository is somewhere else on the network or Internet, only that it is elsewhere. Working with such a remote repository would still involve all the standard pushing, pulling and fetching operations as with any other remote.

Showing Your Remotes

To see which remote servers you have configured, you can run the git remote command. It lists the shortnames of each remote handle you’ve specified. If you’ve cloned your repository, you should at least see origin — that is the default name Git gives to the server you cloned from:

If you have more than one remote, the command lists them all. For example, a repository with multiple remotes for working with several collaborators might look something like this.

This means we can pull contributions from any of these users pretty easily. We may additionally have permission to push to one or more of these, though we can’t tell that here.

Notice that these remotes use a variety of protocols; we’ll cover more about this in Getting Git on a Server.

Adding Remote Repositories

We’ve mentioned and given some demonstrations of how the git clone command implicitly adds the origin remote for you. Here’s how to add a new remote explicitly. To add a new remote Git repository as a shortname you can reference easily, run git remote add :

Now you can use the string pb on the command line in lieu of the whole URL. For example, if you want to fetch all the information that Paul has but that you don’t yet have in your repository, you can run git fetch pb :

Paul’s master branch is now accessible locally as pb/master — you can merge it into one of your branches, or you can check out a local branch at that point if you want to inspect it. We’ll go over what branches are and how to use them in much more detail in Git Branching.

Fetching and Pulling from Your Remotes

As you just saw, to get data from your remote projects, you can run:

The command goes out to that remote project and pulls down all the data from that remote project that you don’t have yet. After you do this, you should have references to all the branches from that remote, which you can merge in or inspect at any time.

If you clone a repository, the command automatically adds that remote repository under the name “origin”. So, git fetch origin fetches any new work that has been pushed to that server since you cloned (or last fetched from) it. It’s important to note that the git fetch command only downloads the data to your local repository — it doesn’t automatically merge it with any of your work or modify what you’re currently working on. You have to merge it manually into your work when you’re ready.

If your current branch is set up to track a remote branch (see the next section and Git Branching for more information), you can use the git pull command to automatically fetch and then merge that remote branch into your current branch. This may be an easier or more comfortable workflow for you; and by default, the git clone command automatically sets up your local master branch to track the remote master branch (or whatever the default branch is called) on the server you cloned from. Running git pull generally fetches data from the server you originally cloned from and automatically tries to merge it into the code you’re currently working on.

From git version 2.27 onward, git pull will give a warning if the pull.rebase variable is not set. Git will keep warning you until you set the variable.

Pushing to Your Remotes

When you have your project at a point that you want to share, you have to push it upstream. The command for this is simple: git push
. If you want to push your master branch to your origin server (again, cloning generally sets up both of those names for you automatically), then you can run this to push any commits you’ve done back up to the server:

This command works only if you cloned from a server to which you have write access and if nobody has pushed in the meantime. If you and someone else clone at the same time and they push upstream and then you push upstream, your push will rightly be rejected. You’ll have to fetch their work first and incorporate it into yours before you’ll be allowed to push. See Git Branching for more detailed information on how to push to remote servers.

Inspecting a Remote

That is a simple example you’re likely to encounter. When you’re using Git more heavily, however, you may see much more information from git remote show :

Renaming and Removing Remotes

If you want to remove a remote for some reason — you’ve moved the server or are no longer using a particular mirror, or perhaps a contributor isn’t contributing anymore — you can either use git remote remove or git remote rm :

Once you delete the reference to a remote this way, all remote-tracking branches and configuration settings associated with that remote are also deleted.

Managing remote repositories

In this article

Learn to work with your local repositories on your computer and remote repositories hosted on GitHub.

Adding a remote repository

To add a new remote, use the git remote add command on the terminal, in the directory your repository is stored at.

The git remote add command takes two arguments:

For more information on which URL to use, see «About remote repositories.»

Troubleshooting: Remote origin already exists

This error means you’ve tried to add a remote with a name that already exists in your local repository.

To fix this, you can:

Changing a remote repository’s URL

The git remote set-url command changes an existing remote repository URL.

Tip: For information on the difference between HTTPS and SSH URLs, see «About remote repositories.»

The git remote set-url command takes two arguments:

Switching remote URLs from SSH to HTTPS

You can use a credential helper so Git will remember your GitHub username and personal access token every time it talks to GitHub.

Switching remote URLs from HTTPS to SSH

Troubleshooting: No such remote ‘[name]’

This error means that the remote you tried to change doesn’t exist:

Check that you’ve correctly typed the remote name.

Renaming a remote repository

Use the git remote rename command to rename an existing remote.

The git remote rename command takes two arguments:

These examples assume you’re cloning using HTTPS, which is recommended.

Troubleshooting: Could not rename config section ‘remote.[old name]’ to ‘remote.[new name]’

This error means that the old remote name you typed doesn’t exist.

Troubleshooting: Remote [new name] already exists

This error means that the remote name you want to use already exists. To solve this, either use a different remote name, or rename the original remote.

Removing a remote repository

Use the git remote rm command to remove a remote URL from your repository.

The git remote rm command takes one argument:

Removing the remote URL from your repository only unlinks the local and remote repositories. It does not delete the remote repository.

These examples assume you’re cloning using HTTPS, which is recommended.

Note: git remote rm does not delete the remote repository from the server. It simply removes the remote and its references from your local repository.

Troubleshooting: Could not remove config section ‘remote.[name]’

This error means that the remote you tried to delete doesn’t exist:

Check that you’ve correctly typed the remote name.

Help us make these docs great!

All GitHub docs are open source. See something that’s wrong or unclear? Submit a pull request.

git remote set-url to change remote repo URL [With Examples]

Table of Contents

Using git remote set-url to change remote repository URL

It is inevitable to push changes that you make in your local project upstream while using git. In the process, you may require to use the git remote set-url function if you want to push the changes to a different URL. This could be because you changed your user name or you want to move the project to a new repository. Git has provided reliable means to run such operations without affecting the project progress or the work of other collaborators.

In this tutorial, we will practice how to change a remote URL without running an error supported by examples.

git remote set-url syntax

Following is a basic syntax which we will use through out this article to change remote URL. For complete list of supported options you can check official git documentation.

Git workflow to change remote URL

Following are the brief steps required to change a remote URL properly in git

Setting up the lab environment

Before we can practice using the git remote set-url command, we shall first prepare our lab environment. We will clone a remote project git-url to our local work station windows 10 pro. We will also be using git version 2.32.0.windows.2 to run this experiment.

Below is the sample output for the git clone command.

How to change remote URL to repo with new account user name

Let’s assume we had issues with the current git account and had to change the user name from Maureen-M to Josephine-M-Tech after cloning. Such a change will affect the process of pushing your commits upstream. Your local changes will still be using your old username and will require you to update the changes to the new user name.

It is such a scenario that will prompt you to use the git remote set url command. Let put that into practice as follows:

Using the active project git-url we shall run a few commits and try to push the changes upstream to see what happens.

To view the current remote URLs before changing the git account username we shall run the git remote –v command as shown below:

Now let’s add a few commits to the local project git-url before pushing upstream

Note the message where git informs you that the repository moved and you will have to use the new location.

To view the set remote URL we shall run git remote –v command again:

It’s a success! We now have a new remote URL set using the git remote set-url command.

Understand that git can automatically update the new changes by linking the two URLs which you can still work with. An issue may however arise if the old username URL is taken by someone else and the link becomes broken.

To view the set URL in action, let’s make changes to the committed file and push upstream using the active branch newbranch as follows:

You notice the new push action no longer has a warning message about the change in URL as it has been updated.

How to add a remote URL from the local repository

To set a remote URL from a local repository use the git remote add command as demonstrated below:

We will use the master branch in the git-url project for this example.

Next, we shall run git remote –v command to view all the present remote as shown below:

To set another remote from the local repository we shall run the following:

We shall run the git remote –v command to view all the remotes URLs available as shown below:

The remote new-username url has been added.

How to push new commits upstream using git remote set URL

To understand how to push commits into the set remote URL new-user we shall commit some changes to the active branch master as follows;

Next, we will run the git status function to confirm if the changes were successfully pushed upstream.

The status confirms a clean working tree and therefore the push procedure was a success.

How to delete a remote URL in git

To remove a remote URL you will use the git remote remove command. In this example, we are going to remove the new-user URL as follows;

Let’s view the current URLs as shown:

We will then run the git remote –v command to confirm the removal of new-user as demonstrated below:

From the output, we no longer have the new-user URL among the list of remote URLs.

How to set a remote SSH URL in git

To set a remote URL if you have SSH configured GitHub a count follows the same process as changing the remote URL. You will insert the new SSH-remote-url in place of the new-remote-url as shown in the syntax below.

Here is an example of how the SSH URL looks like:

We have set a new URL origin using git SSH URL

Summary

We have covered the following topics relating to git remote set URL:

Further Reading

Related Posts

Didn’t find what you were looking for? Perform a quick search across GoLinuxCloud

If my articles on GoLinuxCloud has helped you, kindly consider buying me a coffee as a token of appreciation.

For any other feedbacks or questions you can either use the comments section or contact me form.

Thank You for your support!!

How to Change a Git Remote

You can change a Git remote URL using the git remote set-url command. Navigate to the repository whose remote URL you want to change and then execute this command. The set-url command accepts two arguments: the remote name and the new repository URL.

Have you changed the name of a remote Git repository? Are you moving a remote repository to another location? Both of these operations will change the URL of a Git repository. This will cause any references to your remote repository to break.

Do not worry! The git remote set-url command is here to the rescue. This command allows you to change the URL of a remote repository.

In this guide, we’re going to talk about what git remotes are and how you can change a git remote. We’ll walk through an example to help you get started.

What is a Git Remote?

A Git remote is a pointer that links your local version of a repository to a remote repository.

Git is a distributed version control system. This means that multiple developers can keep their own copies of a project on their own machines. The changes that you make to a repository will only be accessible by other developers when you push them to a remote server.

A Git repository can have multiple remotes linked to it. Most repositories only have one remote. Repositories with more than one remote are usually linked to different development environments such as testing, staging, or production.

When you change the name of a repository or move it to another hosting platform, you’ll need to update your remote URLs.

81% of participants stated they felt more confident about their tech job prospects after attending a bootcamp. Get matched to a bootcamp today.

Find Your Bootcamp Match

The average bootcamp grad spent less than six months in career transition, from starting a bootcamp to finding their first job.

Start your career switch today

How to Change a Git Remote

The git remote set-url command changes the Git remote associated with a repository. This command accepts the name of the remote (which is usually “origin”) and the new remote URL to which you want the repository to point.

Let’s start by navigating into a repository:

This command returns:

origin https://github.com/Career-Karma-Tutorials/git-submodule-tutorial (fetch)

Find Your Bootcamp Match

Select your interest
First name

Last name

Email

Phone number

By continuing you agree to our Terms of Service and Privacy Policy, and you consent to receive offers and opportunities from Career Karma by telephone, text message, and email.

origin https://github.com/Career-Karma-Tutorials/git-submodule-tutorial (push)

We have one remote called “origin”. This remote is used to both fetch code from and push code to a remote repository. You should see a similar output when you run this command unless you have multiple remotes set for a project.

We’re going to change the remote of this repository to git-submodule. This is because we have renamed our repository on Github. You can change a remote using the git remote set-url command:

git remote set-url origin https://github.com/Career-Karma-Tutorials/git-submodule

“origin” refers to the name of the remote whose URL we want to change. The URL we have specified is the new URL for the project.

You can specify either a HTTP or SSH URL as a remote. For instance, we could change our link to an SSH URL like this:

git remote set-url origin git@github.com:Career-Karma-Tutorials/git-submodule.git

This will point the “origin” remote to an SSH URL.

Our remotes have been changed:

«Career Karma entered my life when I needed it most and quickly helped me match with a bootcamp. Two months after graduating, I found my dream job that aligned with my values and goals in life!»

Venus, Software Engineer at Rockbot

Find Your Bootcamp Match

origin git@github.com:Career-Karma-Tutorials/git-submodule.git (fetch)

origin git@github.com:Career-Karma-Tutorials/git-submodule.git (push)

Change a Remote Manually

You can change a remote manually by modifying a Git repository’s config file inside your working directory. This approach is practical if you are going to make multiple changes to the configuration of a Git repository.

We can change this code to modify the “origin” remote. Once you have made any changes you need to make, you can save the file.

It is best to change a remote using the Git command. This is because there’s a higher risk that you make a mistake in your configuration file if you alter it manually.

fatal: No such remote ‘[name]’

You may encounter an error fatal: No such remote ‘[name]’ when you try to change the remote of a repository:

fatal: No such remote ‘[name]’

This error occurs when you try to change the URL of a remote that does not exist. To solve this error, make sure you have correctly typed in the name of the remote whose URL you want to change.

Conclusion

Now you’re ready to start changing remotes using Git like an expert!

To learn more about Git, read our complete How to Learn Git guide.

Работа с удалёнными репозиториями

Для того, чтобы внести вклад в какой-либо Git-проект, вам необходимо уметь работать с удалёнными репозиториями. Удалённые репозитории представляют собой версии вашего проекта, сохранённые в интернете или ещё где-то в сети. У вас может быть несколько удалённых репозиториев, каждый из которых может быть доступен для чтения или для чтения-записи. Взаимодействие с другими пользователями предполагает управление удалёнными репозиториями, а также отправку и получение данных из них. Управление репозиториями включает в себя как умение добавлять новые, так и умение удалять устаревшие репозитории, а также умение управлять различными удалёнными ветками, объявлять их отслеживаемыми или нет и так далее. В данном разделе мы рассмотрим некоторые из этих навыков.

Вполне возможно, что удалённый репозиторий будет находиться на том же компьютере, на котором работаете вы. Слово «удалённый» не означает, что репозиторий обязательно должен быть где-то в сети или Интернет, а значит только — где-то ещё. Работа с таким удалённым репозиторием подразумевает выполнение стандартных операций отправки и получения, как и с любым другим удалённым репозиторием.

Просмотр удалённых репозиториев

Если у вас больше одного удалённого репозитория, команда выведет их все. Например, для репозитория с несколькими настроенными удалёнными репозиториями в случае совместной работы нескольких пользователей, вывод команды может выглядеть примерно так:

Это означает, что мы можем легко получить изменения от любого из этих пользователей. Возможно, что некоторые из репозиториев доступны для записи и в них можно отправлять свои изменения, хотя вывод команды не даёт никакой информации о правах доступа.

Обратите внимание на разнообразие протоколов, используемых при указании адреса удалённого репозитория; подробнее мы рассмотрим протоколы в разделе Установка Git на сервер главы 4.

Добавление удалённых репозиториев

В предыдущих разделах мы уже упоминали и приводили примеры добавления удалённых репозиториев, сейчас рассмотрим эту операцию подробнее. Для того, чтобы добавить удалённый репозиторий и присвоить ему имя (shortname), просто выполните команду git remote add :

Получение изменений из удалённого репозитория — Fetch и Pull

Как вы только что узнали, для получения данных из удалённых проектов, следует выполнить:

Данная команда связывается с указанным удалённым проектом и забирает все те данные проекта, которых у вас ещё нет. После того как вы выполнили команду, у вас должны появиться ссылки на все ветки из этого удалённого проекта, которые вы можете просмотреть или слить в любой момент.

Когда вы клонируете репозиторий, команда clone автоматически добавляет этот удалённый репозиторий под именем «origin». Таким образом, git fetch origin извлекает все наработки, отправленные на этот сервер после того, как вы его клонировали (или получили изменения с помощью fetch). Важно отметить, что команда git fetch забирает данные в ваш локальный репозиторий, но не сливает их с какими-либо вашими наработками и не модифицирует то, над чем вы работаете в данный момент. Вам необходимо вручную слить эти данные с вашими, когда вы будете готовы.

Начиная с версии 2.27, команда git pull выдаёт предупреждение, если настройка pull.rebase не установлена. Git будет выводить это предупреждение каждый раз пока настройка не будет установлена.

Отправка изменений в удаленный репозиторий (Push)

Когда вы хотите поделиться своими наработками, вам необходимо отправить их в удалённый репозиторий. Команда для этого действия простая: git push
. Чтобы отправить вашу ветку master на сервер origin (повторимся, что клонирование обычно настраивает оба этих имени автоматически), вы можете выполнить следующую команду для отправки ваших коммитов:

Просмотр удаленного репозитория

Это был пример для простой ситуации и вы наверняка встречались с чем-то подобным. Однако, если вы используете Git более интенсивно, вы можете увидеть гораздо большее количество информации от git remote show :

Удаление и переименование удалённых репозиториев

Если по какой-то причине вы хотите удалить удаленный репозиторий — вы сменили сервер или больше не используете определённое зеркало, или кто-то перестал вносить изменения — вы можете использовать git remote rm :

При удалении ссылки на удалённый репозиторий все отслеживаемые ветки и настройки, связанные с этим репозиторием, так же будут удалены.