Working with Submodule Branches

Git submodules usually point to a specific commit. But what if you need to actively develop inside a submodule?

• This allows independent feature development.
• You can contribute changes back to the submodule's own project.
• It's key for complex projects needing tight integration.

By default, when you clone a project with submodules, each submodule is checked out to a specific commit. This is called a "detached HEAD" state.

• It means you're not currently on any named branch.
• You can view files, but new commits won't automatically belong to a branch.
• It provides a stable way for the parent repo to reference specific submodule versions.