Command Reference

git rm

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

git rm does more than delete a file. It removes the tracked path and stages that deletion for the next commit.

Common patterns

git rm app/old-file.ts
git rm -r legacy-folder
git rm --cached .env.local

Typical scenarios

  • delete a tracked file and commit that deletion
  • stop tracking a file while keeping it locally with --cached
  • remove whole tracked directories with -r

Why it differs from plain rm

You can delete a file with your shell and later stage the deletion another way. git rm simply bundles the file removal and staging step together.

Practical caution

Once committed and shared, the deletion becomes part of project history, so use it deliberately for tracked paths.

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 log Tutorial

Shows how git log inspects commit history, graph structure, authorship, and filtered history for debugging and review.

Nextgit mv

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