Workflows

Submodule Update Flow

Outline a safe routine for updating submodules, locking revisions, and syncing the parent repository.

Scenario

Outline a safe routine for updating submodules, locking revisions, and syncing the parent repository.

Suggested sequence

  1. Move the submodule to the intended commit
  2. Commit the pointer change in the parent repo
  3. Verify init and recursive update flows

Why this order is safer

The value of a workflow usually comes less from a single command and more from fixing the order of observation, action, and recovery.

Related commands

This topic makes more sense alongside commands such as git fetch, git log, git diff, git merge, git rebase, or git cherry-pick.

Related Reads

fetch vs pull

Explains why fetch-first workflows are often more controllable than pulling directly.

Feature Branch Collaboration

A practical feature-branch workflow for day-to-day teamwork, from cutting the branch and syncing main to cleaning the stack before review.

Sync Before Review

Sync your branch with main before opening review so reviewers see current, focused diffs instead of stale base noise.

PreviousMaintaining Long-lived Branches

Show how long-lived branches can stay aligned with main and avoid painful late merges.