JIYIK CN >

Current Location:Home > Learning > OPERATING SYSTEM > Git >

Difference between Git Checkout --Track Origin/Branch and Git Checkout -B Branch Origin/Branch

Author:JIYIK Last Updated:2025/04/03 Views:

This article outlines the difference between the git checkout -b branch origin/branchand git checkout --track origin/branchcommands. We use these two commands to check out remote branches in a Git repository.

These two commands have the same result, but the difference lies in actual usage, as we will see shortly.


Difference between git checkout -b branch origin/branch and git checkout --track origin/branch

To understand the difference between these two commands, we’ll explore what each command does when run on the terminal. Let’s jump right in.

git checkout -b branch origin/branch command

If you are familiar with Git, you must know that we use the following command to check out the remote branch.

$ git checkout <remotebranch>

The above command will create a remotebranch in our local repo and start tracking a remote branch named remotebranch (if your origin has remotebranch ).

What if our local repository already has a remotebranch and we want to create and track a remote branch with the same name? How do we do that?

This is where our git checkout -b branch origin/branchcommand comes into play. We will run:

$ git checkout -b remote-branch1 origin/remotebranch

The command above will create a remote-branch1 in our local repository , tracking remotebranch in our origin . Remember, origin is our remote.

git checkout --track origin/branch command

git checkout --track origin/branchThe command will create a branch called branch and track it in our remote branch. Sounds like the previous command, right?

The question is, when should you use it?

It is better to use the command above if our local repository contains multiple remotes with the same branch name.

Let’s look at an example.

Assume our local repository has four remote repositories and a branch called remotebranch . As shown below, we can set up a branch to track one of our remotes, in this case origin.

$ git checkout --track origin/remotebranch

The command above will create a local branch called remotebranch and track it based on remotebranch in our source .

In short, git checkout -b branch origin/branchthe and git checkout --track branch origin/branchcommands have the same result, i.e. creating a branch to track the remote.

As we discussed, the difference lies in the actual use of the two.

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.

Article URL:

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

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

Scan to Read All Tech Tutorials

Social Media
  • https://www.github.com/onmpw
  • qq:1244347461

Recommended

Tags

Scan the Code
Easier Access Tutorial