The general syntax is the following: $ git pull īoth the and parameters are optional, as long as your current branch is tracking a remote one. In this section, after I describe the difference between fetch and pull, I'll also briefly talk about the numerous different ways the command can be used. By that I mean that it performs the actions of a few other Git commands in sequence, which I'll explain more about below. The git pull command is what I'd call a "high level" command. Now that we've seen what fetch does and a bit about how it works, let's take a look at pull. Note that this is considered a "safer" method than pull since it does not actually make any changes to your local branches. This will allow you to see the changes, and it still isn't merged in to any of your own branches.Ī quicker way to view these changes would be to just look at the commit logs, which you can do with: Now that you have the changes in your repository, you'll likely want to actually view them, which you can do by just checking out the branch: $ git checkout origin/master To do this you could use the following commands: $ git fetch origin master So, let's say you want to view changes for the "master" branch from the "origin" remote repo before deciding to merge them in to your repo. This is because Git keeps fetched content separate from your own repo's content until it is merged in.
No working changes will be lost, and you'll see no direct affect on your local branches. The interesting thing about the fetch command is that it doesn't actually affect anything in your local repo. If this parameter is omitted then changes from all branches are retrieved.
Specifying will only fetch changes from that branch.
0 kommentar(er)
