Command Reference

git mv

Rename or move tracked files while keeping the index in sync, which makes large refactors easier to stage consistently.

git mv renames or moves a tracked file and stages that path change at the same time.

Common examples

git mv old-name.ts new-name.ts
git mv docs/guide.md docs/intro.md

When it helps most

  • during rename-heavy refactors
  • when you want file movement and staging to happen in one step

How to think about it

Git still reasons primarily about content plus paths. git mv is mainly a convenience command that keeps your working tree and index aligned cleanly.

Useful reminder

Git can often infer renames even if you use your shell mv first. The main value of git mv is clarity and staging convenience.

Related Reads

git init Tutorial

Explains how git init creates a repository, how the initial branch is defined, and how it is used for both new and existing directories.

git clone Tutorial

Explains how git clone copies a repository, what origin means by default, and what local branch setup usually looks like after cloning.

git status Tutorial

Covers how git status shows working tree, staging area, and branch state, and why it should be part of nearly every Git workflow.

Previousgit rm

Remove tracked files and stage that removal, which makes it easier to separate filesystem deletion from Git history changes.

Nextgit fetch Tutorial

Explains how git fetch updates remote refs, why it is often safer than pull, and where it fits in a daily sync workflow.