Worktree
Also called git worktree, working tree.
In plain English
A worktree is an additional working folder attached to the same GitGit is a version-control tool that records changes to files and helps people combine work over time. repositoryA repository is a project's stored files and their recorded change history, commonly managed with Git..
Example
You keep one folder on the branchA branch is a named line of snapshots, so a new idea can grow beside the shared line. you are reviewing and open a second folder to try a fix. Saving a file in the second folder does not change the first.
Why it matters
Each worktree has its own checked-out files. People often put each worktree on its own branchA branch is a named line of snapshots, so a new idea can grow beside the shared line. so the folders do not fight over one checkout. GitGit is a version-control tool that records changes to files and helps people combine work over time. does not require every worktree to be on a separate branch.
Commits from every worktree still belong to the same repositoryA repository is a project's stored files and their recorded change history, commonly managed with Git.. Deleting a worktree folder does not delete those commits.
Common confusion
A worktree is not a second copy of the repositoryA repository is a project's stored files and their recorded change history, commonly managed with Git.'s history. It is another working folder on the same repository.
Sources
Updated September 30, 2026.