Worktrees and Submodules

Worktrees & Submodules

Both have their own sections in the Nav Pane.

Worktrees

A worktree is an extra folder with a different branch checked out, sharing the same repository. It lets you work on several branches at once — say, a fix on main while a feature is half done — without stashing or switching.

• The Worktrees section lists the repository's worktrees and the branch each has checked out.
• Add worktree checks out an existing branch, or a new one you name, in a new folder. The folder goes next to your repository by default, named after the repository and the branch; you can choose a different parent folder.
• Open opens a worktree as its own repository tab.
• Remove deletes a worktree's folder, after confirming. Its commits and branches stay in the repository. If the folder is already gone, the worktree is simply forgotten.

A branch checked out in one worktree can't be checked out in another. The branch list marks those branches, and trying to check one out says it's checked out in another worktree.

Submodules

A submodule is another repository included inside yours at a specific commit. The Submodules section appears only in repositories that have them.

• Each submodule shows its path, and its state when it needs attention: not initialised, different commit (it's checked out at a commit other than the one your repository records), or conflicted.
• Update checks a submodule out at the commit your repository records, initialising it (and any submodules inside it) first if needed. Update all does every one. Updating can be cancelled.
• Open opens a submodule as its own repository tab.

When a commit or your working copy changes which commit a submodule points to, its diff lists the commits it moved between, instead of two commit hashes.

Git LFS

Files stored with Git LFS are labelled LFS in Working Copy, and their diffs show the size change instead of the pointer text Git stores. If Git LFS isn't installed, the diff says so. See The Diff Viewer.