fetch

Fetches origin updates for target repositories.

Usage

git-wrangler fetch [--repo <path>] [--prune] [--guided]

What it does

Discovers Git worktrees under the current directory, or targets exactly one worktree with --repo, and runs git fetch origin in each repository.

Use this when you only want to update remote-tracking refs. It does not merge, rebase, or otherwise change working tree files.

This is the explicit fetch command. Remote-aware reporting and history rewrite planning commands perform their own built-in git fetch --prune origin refresh by default unless --no-fetch is set.

Options

FlagRequiredDescription
--repo <path>OptionalTarget exactly one repository instead of discovering recursively.
--pruneOptionalPrune remote-tracking branches that no longer exist on origin.
--guidedOptionalInteractively configure command options before execution.

Examples

# Fetch updates for all repositories
git-wrangler fetch

# Fetch and prune stale branches
git-wrangler fetch --prune

# Fetch updates for a specific repository
git-wrangler fetch --repo /path/to/repo

Notes

  • Missing or invalid origin remotes are per-repository failures and count in the final summary.
  • Each repository’s remote git fetch operation has a 30-second timeout.
  • Routine success lines are suppressed to keep console output clean.