* master 5dcc5f5 README.md edited online with Bitbucket The following “git branch” retrieve you the branch details the exists local and reference to remote. Think of them as bookmarks, to remind you where the branches in your remote repositories were the last time you connected to them. They’re local references that you can’t move Git moves them for you whenever you do any network communication, to make sure they accurately represent the state of the remote repository. Remote-tracking branches are one of the remote references to the state of remote branches. # cd git-exercise/ # git ls-remoteĥdcc5f579f26dd160acf1e8d2b457d072e6f4579 refs/heads/master # git remote showĪbove marked bold letters sentence are remote reference and will see in details as we progress. You can get a full list of remote references explicitly running command git ls-remote, or git remote show for remote branches as well as more information. Remote: Total 9 (delta 2), reused 0 (delta 0) Remote: Compressing objects: 100% (8/8), done. Let’s do a git clone to local machine, # git clone into 'git-exercise'. I have forked one of my repository to demonstrate and named the new repository as “git-exercise”.
I’m going to deal with remote reference taking a public remote repository clone to my local machine and manipulate to understand the version transition between my machine to origin remote repository.
Remote references are reference in the form of branches,tags and so on to a simple pointer on your remote repositories.
#Git fetch vs pull origin how to#
In the follow of git articles,this one to take more new git terms and ideas that git offers to stand as being the best version system designed by Linus Torvalds.īefore discussing git fetch and git pull,i would take a chance to say about remote reference and how to deal with it.
0 kommentar(er)
