Using `git Submodule Update`
Let's say I have
project_a (git repo), which contains files & another
project_b (git repo).
project_a --> files --> project_b
As the git-scm book demonstrates, I can run:
cd project_a git submodule init git submodule update // clones project_b repo specified in '.gitsubmodules'
to populate the initially empty
project_b directory within
Rather than run
git submodule update to get the latest from
project_b, I'd prefer to clone the latest version of
project_b at a point in time, and then have
project_a only use that version (unless, of course, I do a
git pull in
How can I do this?
What you're describing is exactly how submodules already work in git. If you don't update the hash for the submodule and check it in to
project_a, you'll always use the same revision of
- → Authenticate with a cookie using laravel 5.1 and jwt
- → Finding a specific GitLab tag from PHP
- → React: How to publish page on server using React-starter-kit
- → babel-loader, webpack, ES2015 modules: "Element type is invalid"
- → Create a function-attribute of a function, which is, in its turn, a method of an object literal
- → Model Validation in laravel 5.1 not working
- → GIT fatal: loose object
- → Laravel validation required rule not working
- → Axios array map callback
- → Where does this `webpack://` come from for `webpack-dev-middleware`?
- → error when trying to modify project in laravel forge
- → GitHub Pages and Jekyll content duplication and SEO issues
- → Use Laravel repositories with Datatables