Git submodules peer2peer workflow -


i have tools collection sync between computers via git pull on remote repo working tree.

whenever of tools have git source add them 'git submodule add' .

sometimes small modifications, compile tools, , add want commit in git repo - aim use them fast possibility recompile. proper workflow that? if start with:

modulepath/submodulepath/bin$ git add submodulefile modulepath/submodulepath/bin$ git commit -m "subfix" modulepath/submodulepath/bin$ git pull origin master modulepath/submodulepath/bin$ cd ../../ modulepath/$ git add submodulepath;git commit -m "subfix in sub" 

then commit subfix propagated after pull main repo ? i've read here git submodule update need commit first submodule. fact commit won't pushed submodule origin want sync change between hosts sharing main module, how proceed? possible overlay changes in submodule main module? or can start submodule branch without upstream url - fetched/merged parent main module.

but fact commit won't pushed submodule origin want sync change between hosts sharing main module

that issue here: need push first submodule if want main repo able back.

the main repo record gitlink (special entry in index) representing new sha1 of submodule.
if sha1 represents commit not pushed submodule, git submodule update won't able succeed.


Comments

Popular posts from this blog

sql - VB.NET Operand type clash: date is incompatible with int error -

SVG stroke-linecap doesn't work for circles in Firefox? -

python - TypeError: Scalar value for argument 'color' is not numeric in openCV -