He or she makes all updates with one atomic commit to such repository, and they are distributed automatically on the server between the project and the shared libraries. If you do an initial submodule update, commit in that submodule directory without creating a branch to work in, and then run git submodule update again from. It’s similar to Git Submodules, but has a very important difference: the repositories are nested on the server’s side.įor the end-user, it’s just a regular repository, with all code needed for his or her project (and nothing except that). While dozens of engineers struggle online in the monorepo/multirepo battles, another approach is possible – Git X-Modules. When you do the commit, the index will update the commit string for the submodule.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |