submodule-dev-flow

Preventing Git submodule checkout collisions involves isolating feature work in per-feature worktrees while keeping the main submodule checkout under vendor read-only. Merge submodule PRs first, then bump pointers on master.

Parallel multi-submodule development workflow follows these steps: sync master, create a per-feature worktree, install dependencies and run checks, commit and push, open a PR, then bump the submodule pointer on master.

Yes, you can use Git worktrees to manage multiple submodule features simultaneously by creating a dedicated worktree for each feature. This isolates changes and maintains a clean master in the control-center repository.

You should bump submodule pointers on master only after the corresponding submodule PRs have been successfully merged. This enforces a deterministic workflow and keeps the control-center master branch clean.

Submodule checkouts break when switching branches due to Git collision conflicts. Using a pinned, read-only submodule checkout under vendor and separate worktrees for feature work prevents these collisions.