Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Surviving Git Submodules [Diagram]

DZone's Guide to

Surviving Git Submodules [Diagram]

Like so many other things, working with submodules in Git is so much easier when you know how.

· Integration Zone
Free Resource

Share, secure, distribute, control, and monetize your APIs with the platform built with performance, time-to-value, and growth in mind. Free 90-day trial of 3Scale by Red Hat

I'm a fan of submodules in Git, but sometimes it seems like I'm the only one! After having worked with this approach on a few projects, I'm coming to the conclusion that, like so many other things, it's easy when you know how. So, I tried to take my handwavy explanation of how to work with submodules and turn it into a handy diagram for you.

Surviving Submodules

The basic premise is this: remember that you need to commit to both the parent project and the submodule. Do the submodule first. You need to update the submodule when you update your main project. Stay away from git add . because it's alarmingly easy to revert submodule changes.

Explore the core elements of owning an API strategy and best practices for effective API programs. Download the API Owner's Manual, brought to you by 3Scale by Red Hat

Topics:
git ,submodules ,integration

Published at DZone with permission of Lorna Mitchell, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}