Suddenly, all the commands you used to know must be done differently and with more of them. Remembering the good old days when we all knew what to type But here you are, juggling multiple versions of the same files. You might mutter to yourself that the entire point of having version control was to avoid this exact situation. Putting this all together for code review becomes a massive headache. Other times, different sets of changes from different developers wind up in different versions of the submodule, across different instances of the repository. But it has to be managed meticulously or projects can break and hours of work can just vanish. If that sounds tedious, that’s because it is. So, if a developer updates a submodule used in five other repositories, the developer has to update every single one of them. Every version of the parent repository is tied to a particular version of the submodule. Much of the difficulty comes down to this: Git submodules don’t just sit inside parent repositories. It slowly dawns on you that Git is really complicatedĪnd now you – and your whole team – have no choice but to be really good at it. Your mind was on what you wanted to build. After all, this wasn’t the bit that really excited you. That might have been as much as you thought about it. You type one command and it’s up and running. Well, that’s just what Git submodules are for, right? The shared code has its own repository, which sits inside a parent repository for every application that uses it. You want a way to work on everything together. The last thing you want is to waste time developing different versions of that code. Git X-Modules lets you enjoy the speed, scale and simple sharing of Git submodules without the bit that drives you to delirious madness
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |