How to "freeze" a git submodule

I am using multiple repos that I do not have and I think what if I deploy my application while they are not available? It just can't happen.

Is there a way to "freeze" a submodule in some way that when I pull from my repository the submodules are already init and updated?

Any help is appreciated.

+2


source to share


2 answers


I am using multiple repos that I do not have and I think what if I deploy my application while they are not available? It just can't happen.



Build your mirrors of these repositories by cloning them and use your mirrors as submodules.

+4


source


If you have no intention of tracking development in the subodule'd repository, why configure it? Submodules are meant to keep the external development of a repository separate from your own. I would just check whatever you want to "freeze" it and push to your main repository. This can be done with a subtree merge strategy that focuses more on including an external repository and then works with the entire history of the merged repositories together.



If you said that when you deploy / free I would never rely on external repos and your bleeding related development sources and just run the release archive / tarball / executable / whatever you release, ve already got the submodule source , it becomes a non-problem, although in any case this problem is also mitigated by the subtree merge strategy.

+2


source







All Articles