Is anybody here using Tower for Kirby developing with Git? If so I’d be glad if someone could explain how to do updates. I learned everything else I wanted to know from this tutorial: Design & Develop Your Own Blog. But I’m not sure how to update the submodules from within tower. Especially how to handle the toolkit which is a submodule of the kirby submodule …
Yes I know that. But let’s say theres an update for the kirby submodule, do I have to update the toolkit manually or is this automatically included in the update of kirby.
Or can I just set all submodules to master branch and Tower does the rest?
No. Tower is just a GUI client for git and does not do any magic.
Pulling one submodule (kirby in this case) only updates the files of the repository itself and does not checkout the appropriate commit of its submodules.
I use Tower for merging and committing parts of the code (a GUI tool is great for that), but for updating submodules, I use the command git submodule update --init --recursive after pulling the kirby and panel submodules to make sure that everything gets updated to the appropriate commits. That’s actually faster than clicking around in Tower.
Then I’ll have to do this operation inside a submodule? Because in my lets call it root repo when right clicking on a submodule I can only fetch? Or is it because there’s nothing to pull at the moment?
Ok here’s a picture of my Tower/Kirby usage. the right-click menu show which branch you have checked out. I’m on the master here, but you can also swap to a tag, and then swap checkout a new tag when you feel ready. Fairly sure update “panel” is not greyed out if there is something to pull, or might just need to do a 'Fetch “panel” ’ first.