ฝัง
- เผยแพร่เมื่อ 6 ต.ค. 2024
- In this Git tutorial, learn what submodules are and when you should use them.
If you're looking for a good Git GUI client to help make working with Git more intuitive, check out GitKraken!
Download GitKraken free at bit.ly/2ExnR6K
#git #gitkraken #gitclient #gitgui #learngit #programming #github #bitbucket #gitlab
This is the only useful video I've found on submodules so far. Everyone keeps beating around the bush, and I never get anything out of watching those videos. Thanks for being very precise and short in what a submodule is. If you also have a video on subtrees as well, so I can figure out which of the two to use, that'd be brilliant. I'll have a look on your channel! :-)
Doesn't look like you have a video titled "All About Subtrees"? - New video suggestion. :-)
a very simplified explaination. Thanks
This was a great introduction to the concept of submodules in Git. Thanks for sharing!
Best explanation without fuffing about
Short and informative, thx!
Thank you, easy to understand and elegant!
Great tutorial, I am using submodules all the time, so made a video and blogged too :) Thanks for tutorial.
Thank you so much! That was exactly the piece of information I needed :)
This was great, thank you!
Cool explanation but where is the rest of "All About Submodules"?
How do I set it up from scratch? What commands I have to do? Practical example?
Great explanation and handy tool.
Question: Lets say you own "repo A" and you want a submodule to "repo B" that another group manages. What happens if you need to add something to the submodule (repo B) that the original owner of "repo B" deems unwanted or ridiculous and doesn't want you to even have that commit in an independent branch on their remote since the commit is not deemed useful for the rest of "repo B" userbase. How would you make that submodule commit available to the rest of the users of "repo A" if "repo B"'s owners deny the remote push?
The owners of "repo A" would fork "repo B" into "repo C" and then update the submodule to point to "repo C" instead of "repo B". Then the owners of "repo A/C" can push any changes they want.
@@GitKraken Thank you for the reply. At that point, if the organization owning "repo A" only needed to use "repo B" (or C) as a subcomponent of "repo A" and not for that organization's other repos, I'm guessing that a subtree may be easier to maintain everything in one place. I know this is getting into the design decision territory, but it sounds like a subtree would usually be better for cases where unapproved changes to a dependency repo may be required (unless you are willing to go through the overhead of forking and maintaining that fork). I'm thinking of which cases minimize repo maintenance and reduce training time for onboarding new developers when you only have guaranteed control over "repo A" with the option to fork other repos if you're willing to pay the maintenance cost.
Very well explained. thx
Thanks for the information
What happens if the repo I add as a submodule ceases to exist? Does it break horribly or can I just upload my local copy of the submodule to a new repo, change the origin and everything works again?
What about when the submodule repo is the same module where you develop? Headaches..
Headache is an understatement....
Hi.
What happens if i do change inside submodule a file and i want update the main root
for example:
/proyect main
submodule /proyect @ d4b9dc90
@d4b9dc90 this should will change
pd: zorry my english ..
regards
Thanks for the information! Didn't even know about that :D
i don't understand the problem this solves. package managers already solves this problem afaik. is this for the case where there's no package manager?
Awesome video! I like it
All about submodules? "All"?? Really? No explanation of syncing, pushing your changes. No git commands. No examples. This is not "all". This is "blah".
If you make changes to the code in the submodule, and then changes are made in the main repo, can you merge the changes from the main into the sub without overwriting your own changes?
Thank you
This will not work for me because the sub modules are my own code and I need both to be updated.
3:00 That's really NOT all that there is. You never address how to handle your changes to files in a submodule.
I'm too new. I did not understand any of this. LOL.
Blah but gives some intro :D
Cool video explaining the concept but it is NOT a TUTORIAL.
This video didn't include any information on the command 'git submodule' nor its features - nor did it show anything about how it works using git's GUI (though personally I don't use that, so I wouldn't know if it has that feature available). That'll be a thumbs down from me.
👋🏼Thanks for taking the time to comment. This video is meant to discuss the submodule conceptually, which is why it does not cover any commands. However, I'll make a note of this for future video topics 📝
@@GitKraken Thank you for taking this into consideration.
Awesome video! I like it