Stop tracking a remote branch in Git
This article explains how we can stop tracking a remote branch in Git. By now, you must be very familiar with the concept of tracking remote branches.
This session will cover the various methods you can use to stop tracking a remote branch. Let's jump right in.
Stop tracking a remote branch in Git
This is a list of all the remote-tracking branches in our repository.
If you recall, newer versions of Git will show remote tracking branches in blue. So we can see that Dev2.1 in our local repository is tracking Dev2.1 in our remote origin.
We can stop tracking a remote branch using the following steps.
First, we will checkout the Dev2.1 branch as shown below.
$ git checkout Dev2.1
We can now run the following command to stop tracking the remote branch.
$ git branch --unset-upstream
As soon as we execute the command, our Dev2.1 will stop tracking the remote branch. Let's check if this is the case.
We can see that our Dev2.1 branch has no remote-tracking branch.
请注意
, when you stop tracking a remote branch, you will no longer be able to push changes made in your local repository to the remote branch.
Other options
Alternatively, you can delete the remote-tracking branches in your local repository. This doesn't work for everyone.
This is a quick solution for those who no longer need branches.
$ git branch -d -r origin/<remote branch name>
Replace the remote branch name with the name of the tracking branch. This command does not delete the branch in the remote repository.
It only unsets the branch used to track the remote.
Another way to handle this is to edit the configuration file to remove the link between the local and remote branches.
Run the command below.
$ git config --unset branch.<local-branch-name>.remote
$ git config --unset branch.<local-branch-name>.merge
This will edit the configuration to remove the association between the remote and local branches.
In short, we have covered three methods that can be used to stop tracking a remote branch. git branch --unset-upstream
The command is the cleanest and simplest.
You can also remove the link between two branches by editing the Git configuration file.
For reprinting, please send an email to 1244347461@qq.com for approval. After obtaining the author's consent, kindly include the source as a link.
Related Articles
Git installation and establishment of local warehouse service
Publish Date:2025/04/05 Views:89 Category:Git
-
Git is a distributed version control system: the client does not only extract the latest version of the file snapshot, but also completely mirrors the original code repository. It has the following advantages: a. Since every extraction oper
git remote operation——multiple remote repositories for one project
Publish Date:2025/04/05 Views:131 Category:Git
-
Multiple remote repositories for a git project In our git project, the command to operate the remote repository information is $ git remote # 查看当前所有的远程仓库的名称 $ git remote -v # 查看远程仓库的名称和远程仓
Git cherry pick command usage
Publish Date:2025/04/05 Views:190 Category:Git
-
git cherry-pick is a powerful command that allows us to select an arbitrary Git commit by reference and attach it to the HEAD of the current working branch. Cherry picking is the act of picking a commit from one branch and applying it to an
Comparison between Git merge and Git rebase
Publish Date:2025/04/05 Views:171 Category:Git
-
The git rebase command may seem like Git wizardry to beginners, but if used carefully, it can actually make life easier for your development team. In this article, we compare git rebase with the related git merge command and identify all th
How to fix Git error Error: src refspec master does not match any
Publish Date:2025/04/05 Views:124 Category:Git
-
When using Git, we may encounter the error "src refspace master does not match any". Here's what the error means and how to fix it. What does src refspec master does not match any Mean in Git mean? We may encounter this error when we try to
Rebase local branch when pulling changes from remote repository branch in Git
Publish Date:2025/04/05 Views:144 Category:Git
-
This article will cover the basics of rebasing your local branch when pulling changes from a remote repository branch in Git. We use the version control system Git to track changes made to files. We commit changes in a local branch in our l
Undo Git Stash
Publish Date:2025/04/04 Views:187 Category:Git
-
This article explains how to make and save changes to a repository. Git allows you to save changes locally and push them to a server when needed. In Git, we don't use the term save , but commit . We use git add , git commit , and git stash
View a list of cache entries in Git
Publish Date:2025/04/04 Views:59 Category:Git
-
We often need to pause our work and focus on something else in our development environment. Therefore, we may need to temporarily save our current work and focus on a different one. We may want to resume our original work later. git stash T
Git stores specific files
Publish Date:2025/04/04 Views:115 Category:Git
-
This article will cover storing changes to only specific files in Git. In Git, when we make some changes in our working tree, we may have some changes which may or may not be staged in our local repo. We may now wish to save these changes f