Renaming a file isn't properly handled in git

I recently used the "Rename" function on a file's context menu in the Refactor submenu. It worked great to update references in my code, but I noticed an issue when I was organizing a commit in git.

The original file was removed and the new one was added thereby destroying version history. This was equivalent to the following comands in Bash:

cat original_file.py > new_file.py
rm original_file.py
prettyPrint(); Instead, this should have been done through git to retain the version history:

git mv original_file.py new_file.py
prettyPrint();
1 comment
Comment actions Permalink
Unlike some other version control systems, there is no difference between these two operations in Git. Git detects renamed files automatically, even if the mv operation wasn't used.

http://stackoverflow.com/questions/7938582/how-does-git-detect-similar-files-for-its-rename-detection
0

Please sign in to leave a comment.