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
git mv original_file.py new_file.py
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.
Dmitry Jemerov, Chief Technology Officer, JetBrains
Why is java eating up so much memory
PyCharm doesn't find Flask-Babel package on a remote Server
Build #178 (Dec/17/2014 3:47PM)