From 08385b16d59e0dc4ec30c05ae77be71dd69d4d3a Mon Sep 17 00:00:00 2001 From: Robert Hafner Date: Mon, 30 Mar 2026 17:45:58 -0500 Subject: [PATCH] Clarify usage of git mv for untracked files Added clarification on using git mv for untracked files. --- {{cookiecutter.__package_slug}}/AGENTS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/{{cookiecutter.__package_slug}}/AGENTS.md b/{{cookiecutter.__package_slug}}/AGENTS.md index b7493f3..621c5f8 100644 --- a/{{cookiecutter.__package_slug}}/AGENTS.md +++ b/{{cookiecutter.__package_slug}}/AGENTS.md @@ -20,7 +20,7 @@ make pre-commit # Install pre-commit hooks git mv old_path new_path # ALWAYS use git mv for moving or renaming files, never use mv or file manipulation tools ``` -**CRITICAL**: When moving or renaming files in a git repository, you MUST use `git mv` instead of regular `mv` or file manipulation tools. This ensures git properly tracks the file history and prevents issues with version control. +**CRITICAL**: When moving or renaming files in a git repository, you MUST use `git mv` instead of regular `mv` or file manipulation tools. This ensures git properly tracks the file history and prevents issues with version control. The only exception to this is if you are moving files which are not tracked in git, as in that case `git mv` will have no effect. ### Testing and Validation