git-module

To manage Git submodules for project maquettes, you can use commands to add, synchronize, list, inspect, or remove submodules. This enforces path conventions like modules/maquette/<module>/<version> to keep dependencies in sync.

The best way to synchronize reusable maquettes stored as Git submodules is by running a sync command. This reduces manual overhead and ensures project dependencies remain perfectly aligned with the enforced maquette path conventions.

The mockmig workflow handles maquette migrations by integrating directly after Git submodule synchronization. It migrates the updated maquettes to ensure project dependencies remain in sync and properly transitioned during versioning updates.

Yes, you can use Git submodules to enforce a specific path convention for project modules. The system strictly enforces the modules/maquette/<module>/<version> directory structure to keep reusable maquettes organized and synchronized.

The available commands for Git submodules representing maquettes include add, sync, list, status, and remove. These commands allow you to manage the entire lifecycle of reusable maquettes within your project dependencies.

You need to integrate submodule synchronization with a mockmig workflow to successfully migrate maquettes after updating dependencies. This integration reduces manual overhead and ensures synchronized submodules are properly transitioned during project migrations.