wrkx-pull

Fast-forward multiple git repositories to their base branch by executing an aggregate pull operation. This uses git fetch and git merge --ff-only across all wrkx.json managed workspaces, updating every repo to the remote tip in a single action without creating merge commits.

Dirty worktrees are reported and skipped during the multi-repo pull process. The sync operation identifies repositories with uncommitted changes, aborts the fast-forward merge for those specific repos, and provides a report of which workspaces need attention before they can be updated.

Yes, you can target a single repository for a focused pull instead of updating all workspaces. This per-repo control allows you to fast-forward one specific workspace to its declared baseBranch tip using the same git fetch and merge --ff-only logic without touching the others.

A fast-forward only merge updates your branch pointer directly to the remote tip without creating a merge commit. Using git merge --ff-only for multi-repo workspaces prevents messy histories and ensures consistency by aborting any updates that would require a true merge due to diverged branches.

Yes, you need locally cloned repositories, a declared baseBranch, a reachable remote, and a wrkx.json configuration file. These prerequisites allow the tool to identify managed repos, execute git fetch operations, and apply the fast-forward merges across the workspace.

Multi-repo pulls abort for diverged branches to preserve your commit history and prevent unwanted merge commits. The tool reports these diverged repositories so you can manually resolve the conflicts, ensuring the workspace sync only succeeds when a clean fast-forward to the baseBranch is possible.