工做中,咱们会用到git pull来从远程仓库"同步"代码,一般有三种方式;git
git pull origin <remote_branch>:<local_branch>
git pull origin <remote_branch>
git pullgithub
这三种用法充分诠释了什么是简即繁,繁即简;看上去简单的,每每背后蕴藏玄机;测试
测试环境: 本地分支:master和dev 远程分支:master和dev $ git branch -a * dev master remotes/origin/HEAD -> origin/master remotes/origin/dev remotes/origin/master
这种用法写起来最为繁琐,但最好理解:fetch
场景:当本地的当前分支不是local_branch;
做用:将远程分支拉取到指定本地分支;url
例如:当前分支是dev,可是你想把远程master”同步”到本地master,但又不想使checkout切换到master分支;
这时你就可使用git pull origin master:masterspa
zhangchangzhi@ZBXXXX /e/02.Workspace-test/gitTest (dev) $ git pull origin master:master From https://github.com/jinxintang/gitTest a09fdc4..941758f master -> master Already up-to-date.
从上述代码能够看到,我当前分支为dev,但执行"同步”操做的倒是在master分支;code
有了上面的例子,这种使用方法的场景和做用就好理解了:orm
场景:在当前分支上进行同步操做;
做用:将指定远程分支同步到当前本地分支;rem
废话不说,上代码:同步
zhangchangzhi@ZBXXX /e/02.Workspace-test/gitTest (dev) $ git pull origin master From https://github.com/jinxintang/gitTest * branch master -> FETCH_HEAD Already up-to-date.
把远程master分支同步到HEAD分支(HEAD分支指向当前位置);
这种写法最简单,也最经常使用,可是隐含的知识也是最多的;
场景:本地分支已经和想要拉取的分支创建了“关联”关系;
做用:拉取全部远程分支的新版本"坐标",并同步当前分支的本地代码(具体根据关联分支而定)
首先咱们先使用git branch -vv
查看一下目前分支的“关联”状况;
$ git branch -vv * dev 1a1b215 [origin/dev] Merge branch 'master' of https://github.com/jinxintang/gitTest into dev master a09fdc4 [origin/master] create pull
能够看到咱们的本地的dev关联的是远程(origin)的dev,本地的master关联的是远程(origin)的master;
那么这种关联是如何创建、是否能够修改呢;
配置本地分支与远程分支的三种方法:
1.检出时创建关联关系:git checkout -b dev origin/dev
当咱们检查时,git会自动为咱们检出的分支和远程分支创建关联关系;
2.提交时配置关联关系:git push -u origin <remote_branch>
或git push --set-upstream origin <remote_branch>
zhangchangzhi@ZB-PF0SB6DQ MINGW64 /e/02.Workspace-test/gitTest (dev_zcz) $ git branch -vv * dev_zcz 3b7001a [origin/dev] cm master a09fdc4 [origin/master] create pull zhangchangzhi@ZB-PF0SB6DQ MINGW64 /e/02.Workspace-test/gitTest (dev_zcz) $ git push -u origin dev_zcz Everything up-to-date Branch dev_zcz set up to track remote branch dev_zcz from origin. zhangchangzhi@ZB-PF0SB6DQ MINGW64 /e/02.Workspace-test/gitTest (dev_zcz) $ git branch -vv * dev_zcz 3b7001a [origin/dev_zcz] cm master a09fdc4 [origin/master] create pull
经过上面的例子能够看到push前dev_zcz关联的是origin/dev,执行push -u 后管理分支改成origin/dev_zcz
注:默认配置下,提交时本地分支需和远程分支同名;
3.更改git/config文件:git branch --set-upstream-to=<remote_branch>
zhangchangzhi@ZB-PF0SB6DQ MINGW64 /e/02.Workspace-test/gitTest (dev_zcz) $ git branch --set-upstream-to=origin/zcz Branch dev_zcz set up to track local branch origin/zcz. zhangchangzhi@ZB-PF0SB6DQ MINGW64 /e/02.Workspace-test/gitTest (dev_zcz) $ git branch -vv * dev_zcz 3b7001a [origin/zcz] cm master a09fdc4 [origin/master] create pull origin/zcz 3b7001a [dev_zcz] cm
不管使用上述那种方法,本地分支和远程分支的“关联”最终都会写到config文件;
zhangchangzhi@ZB-PF0SB6DQ MINGW64 /e/02.Workspace-test/gitTest/.git (GIT_DIR!) $ cat config [core] repositoryformatversion = 0 filemode = false bare = false logallrefupdates = true symlinks = false ignorecase = true [remote "origin"] url = https://github.com/jinxintang/gitTest.git fetch = +refs/heads/*:refs/remotes/origin/* [branch "master"] remote = origin merge = refs/heads/master [branch "dev_zcz"] remote = . merge = refs/heads/origin/zcz [branch "origin/zcz"] remote = . merge = refs/heads/dev_zcz
注:本项目的配置信息存放目录:项目所在目录/.git/config
看完这三种配置关联分支的方法,想必你们已经对“关联分支”有了必定了解;
关联分支:在git中表现为upstream,不管是使用push -u 或是 git branch --set-upstream-to方法,均会将这种对应关系写入.git/config配置文件,若是一个本地分支没有关联分支,则没法执行 git push 或 git pull指令;
没有"关联"分支的状况下,使用push会先让你设置一个upstream branch.
zhangchangzhi@ZB-PF0SB6DQ MINGW64 /e/02.Workspace-test/gitTest (dev_no_upstream) $ git branch -vv * dev_no_upstream 3b7001a cm dev_zcz 3b7001a [origin/zcz] cm master a09fdc4 [origin/master] create pull origin/zcz 3b7001a [dev_zcz] cm zhangchangzhi@ZB-PF0SB6DQ MINGW64 /e/02.Workspace-test/gitTest (dev_no_upstream) $ git push fatal: The current branch dev_no_upstream has no upstream branch. To push the current branch and set the remote as upstream, use git push --set-upstream origin dev_no_upstream
那么创建了一个关联分支,是否就必定能使用git push呢?请阅读<git 实践(二)push的使用>