campaign-commit

To commit changes in a git submodule without breaking synchronization, you must use a submodule-aware commit command that auto-syncs the submodule pointer in the parent campaign repository. This ensures the parent project correctly tracks the updated submodule reference.

A festival commit is a specific git commit type used in campaign workflows that embeds festival traceability metadata into the commit history. It is designed for festival tasks to maintain strict task tracking and governance within the development pipeline.

To choose the right git commit command for campaign tasks, first determine your current context: submodule, festival task, or campaign root. Each context requires a specific commit command to maintain traceability metadata and proper git refs.

Yes, campaign-root git workflows require standard commit commands governed by specific rules to maintain proper refs and campaign-root governance. Using the wrong commit command at the root breaks tracking and synchronization across the project pipeline.

Using the wrong commit command breaks traceability in project development pipelines because different contexts require specific metadata and submodule pointer synchronization. Standard commits lack festival-grade traceability metadata and deterministic submodule handling required by campaign workflows.

The best way to handle deterministic submodule commits during a campaign is to use a submodule-aware commit command that automatically syncs the submodule pointer. This enforces deterministic submodule handling and prevents tracking desynchronization.