Coding & Git

Clone

Also called git clone, repository clone.

A clone is a new copy of a Git repository, history included, created in a new directory.

Example

You clone the repository onto your laptop. You have the commits and a working folder. A teammate's clone is a separate copy. Saving a file in yours does not change theirs until the commits are shared.

Why it matters

Git's clone command copies a repository into a newly created directory, creates remote-tracking branches, and checks out a starting branch. After that, the new directory has its own copy of the history.

A worktree is the nearby idea that is easy to mix up. It is another working folder attached to a repository you already have, not a second copy of that history. Commits made in a worktree still belong to the original repository. Commits in a clone stay in that clone until you share them.

How it shows up on bot.ski

On bot.ski, the pages you read in the browser are not a clone. The site's files and history live in a Git repository, and a person working on that repository can clone it. This glossary already defines Worktree as the extra working folder. This page is the full copy.

Common confusion

A clone is not a worktree. Deleting a clone on your laptop does not delete the original repository. It also does not delete a teammate's clone.

Sources

Updated October 2, 2026.

Cookie preferences