If you run git fetch -prune, however, your Git calls up their Git as usual, lists out all their branch names, and discovers that you have a stale origin/feature/tall, made back when they had feature/tall, and removes it. Now your Git calls up their Git and they don't list a feature/tall.īy default, your Git does nothing about this. Your Git called up their Git yesterday, and created or updated your origin/feature/tall to match their feature/tall. Suppose, for instance, that their Git had a branch named feature/tall yesterday, but no longer has that branch. One problem that occurs here, though, is that they can delete some branch name(s). Note that git branch -a includes git branch -r, but adds the word remotes/ in front of the origin/master names. Running git branch -r will list your remote-tracking names, so git branch -r shows you what your Git saw in their Git, the last time your Git updated using their Git.
When you run git fetch origin (or just git fetch, if there's only one remote named origin), your Git calls up the other Git at that point, obtains any new commits that they have that you don't, and updates all your remote-tracking origin/* names. These names simply remember that, the last time your Git called up the other Git at origin, they said that their master was some particular hash ID. To do this, your Git creates, in your repository, remote-tracking names 1 such as origin/master. Meanwhile, because you Git has called up another Git before, and remembers the URL for that other Git under the name origin, your Git also remembers their Git's branch names.
The commits are the part that your Git shares with other Git repositories, though there is some degree of name-sharing as well. Your Git has your branch names, tag names, and other names, and a collection of commits. Your Git, on your computer, keeps and updates your Git repository. The git remote command is the main user-facing command for working with remotes, but since git clone creates the remote named origin for you initially, you almost never actually need to use git remote. There are additional things you can do with a remote, besides just storing a URL, but storing a URL is sort of the main thing. You can have as many remotes as you like.
The remote itself holds the URL by which your Git calls up some other Git. Remotesīefore we get to the two answers, let's mention that a remote is just a short name like origin. The key issue here is that there are at least two different Git repositories involved. This question has several possible underlying meanings, so it has several possible answers.
0 kommentar(er)
