jj-git-fetch

Fetch the latest changes from the default remote repository

$ jj git fetch

$ jj git fetch --remote [remote]

$ jj git fetch [[-b|--branch]] [branch]

$ jj git fetch --all-remote

jj git fetch [REMOTE...] [OPTIONS...]

REMOTE...
    One or more names of the remote repositories to fetch from (e.g., origin, upstream). If no remote is specified, jj-git-fetch will typically fetch from all configured remotes, mirroring the behavior of git fetch without a specified remote.

OPTIONS...
    These are primarily options passed directly to the underlying git fetch command. jj-git-fetch acts as a wrapper, forwarding these arguments. Common and important options include:
--all: Fetch from all remotes.
--prune or -p: After fetching, remove any remote-tracking branches which no longer exist on the remote.
--tags: Fetch all tags from the remote.
--no-tags: Do not fetch tags, even if configured to.
--dry-run or -n: Show what would be fetched without actually performing the fetch.
--quiet or -q: Suppress progress messages, showing only errors.
--verbose or -v: Be more verbose, showing details of what is being fetched.

The jj-git-fetch command is a specialized subcommand within the Jujutsu (jj) version control system. It serves as a bridge to the underlying Git repository, allowing users to fetch updates from remote Git repositories directly into the jj's Git backend. Essentially, it executes the standard git fetch command with the provided arguments and options.

While jj offers higher-level commands like jj pull (which often includes fetching and rebasing), jj-git-fetch provides direct control over the fetching process, mirroring Git's behavior. This updates the local Git repository's remote-tracking branches (e.g., origin/main), making new commits from the remote available to jj for subsequent operations like updating, rebasing, or merging.

jj-git-fetch only updates the underlying Git repository and its remote-tracking branches. It does not automatically modify your current jj working copy, update local branches, or rebase your history. To integrate fetched changes into your active jj branches, you typically need to follow up with jj update, jj rebase, or use the higher-level jj pull command.

While jj-git-fetch updates the underlying Git repository, jj maintains its own internal representation of the commit graph. After a fetch, new commits from the remote will appear in jj's graph view (e.g., using jj log), typically as remote-tracking branches (e.g., origin/main). These commits are then available for jj's powerful history manipulation and collaboration features, but require explicit jj commands to integrate into local branches.

jj-git-fetch is an integral part of the Jujutsu (jj) version control system, which was designed as a modern, user-friendly alternative to Git, built on top of Git repositories. Introduced as part of jj's core functionality, this command provides a direct interface for synchronizing the jj repository with its upstream Git remotes. Its development reflects jj's philosophy of leveraging Git's robust backend while offering a more intuitive command-line experience. It ensures compatibility and interoperability with existing Git workflows, making it a crucial component for any jj user interacting with external Git repositories.

git fetch(1), jj pull, jj update, jj rebase, jj git push