smflow 0.3.4

Tools and git hooks to make it easier to work with submodules are updated frequently, enable a sort of virtual mono repo.

smflow

smflow is a lightweight toolset and set of Git hooks designed to make working with Git submodules significantly easier. It helps keep submodules in sync with the parent repository, enabling a "virtual monorepo" workflow — without giving up the benefits of repository modularity.

---

🚀 Features

• Intuitively work with submodules through VS Code git interface.
• Automatically attaches submodule HEADs to the commits referenced by the parent repository.
• Quickly see how many changes the current submodule is behind the tracked branch.
• Keeps local submodules in sync when switching branches in the parent project.
• Automatically update .gitmodules in parent when changing locally checking out branches for submodules.
• Configures Git for a smoother submodule experience:
  • Auto-checkout submodules on branch change
  • Auto-push submodule commits when pushing the parent

---

📦 Installation

Note: Requires uv to be installed.

Install smflow with:

uv tool install smflow

🛠️ Usage

From the root of your parent repository (the one that contains submodules), run:

smflow init

This will configure your repository with the appropriate Git settings and install the necessary hooks.

🔍 What smflow init Does

🔗 Git Hooks

The following hooks will be installed: • Post-checkout hook Automatically resets submodules to the correct commit when you checkout a branch in the parent repository. • Post-branch-change hook Updates .gitmodules when you switch between branches, ensuring consistency across the repo.

⚙️ Git Configuration

smflow sets these recommended Git config values:

git config submodule.recurse true

Ensures submodules are automatically checked out when switching branches.

git config push.recurseSubmodules on-demand

Allows pushing submodule commits automatically when pushing the parent repository — if the submodules and parent share the same branch name. If not, Git will warn and suggest pushing submodules first.

⚠️ Limitations

• smflow does not currently support recursive submodules, i.e. submodules within submodules.

🧩 Why smflow?

Managing submodules manually is tedious and error-prone. smflow minimizes the overhead and makes it easier to:

• Stay in sync with your team
• Avoid detached HEAD states in submodules
• Prevent pushing parent branches that reference unpublished submodule commits

Whether you’re working with multiple shared libraries or simply trying to tame Git submodules, smflow provides a smoother, safer workflow.