Propogate file renames in Visual Studio (2013) to GIT as GIT renames?

We use GIT and Visual Studio 2013 (Ultimate + Professional versions). The code for the solution and projects is in GIT and anytime we rename the file in Visual Studio, GIT sees them as

Before rename

c:\temp\testCodeSnippets>git status
# On branch master
nothing to commit (working directory clean)

After rename (from Visual Studio)

c:\temp\testCodeSnippets>git status
# On branch master
# Changes not staged for commit:
#   (use "git add/rm <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#
#       deleted:    OldName.cs
#
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#       NewName.cs
no changes added to commit (use "git add" and/or "git commit -a")

Renaming via git mv

c:\temp\testCodeSnippets>git mv OldName.cs NewName.cs

c:\temp\testCodeSnippets>git status
# On branch master
# Changes to be committed:
#   (use "git reset HEAD <file>..." to unstage)
#
#       renamed:    OldName.cs -> NewName.cs
#

Basically, the renames performed in VS still need some manual work. Equally important; a lot of these renames happen when refactoring from inside the IDE i.e. a class/member/etc gets renamed and all references get changes. If the namespace or classname changes, the files get renamed.

  • Test multiple repos in travis ci
  • How do you preview merge changes in one git command?
  • Google Code Archive to Github
  • “TAG - diff” in gitweb - is it possible?
  • Standard to follow when writing git commit messages
  • Cannot resolve GitHub conflict in PR
  • So, is there any setting to toggle, any tool to install, any deity to appease so that renames from Visual Studio get mapped as renames to GIT too (like git mv does to make it smooth)?

  • Why won't “git reset HEAD” undo my uncommitted, unstaged changes?
  • Count number of lines in a git repository
  • git noob struggling to push development machine changes to remote production server part 2
  • Best Practices Using Git with Visual Studio?
  • Why does git sparse checkout leave behind directories?
  • Cannot `git rm` A Previously Tracked File
  • One Solution collect form web for “Propogate file renames in Visual Studio (2013) to GIT as GIT renames?”

    Core git (the command-line application) only identifies renames by detecting them between files that are staged for addition and files that are staged for deletion.

    Visual Studio, however, does not stage changes you make during operation. Instead, it will stage the changes at commit time. There are several reasons for this, but primary is that staging a change places the file in the object database and doing this for each save would be incredibly costly.

    You will need to manually stage the changes using git add and git rm and your renames will be reported as it always will, by comparing the added changes to the renamed changes.

    (Note that Visual Studio – since it doesn’t stage your changes as you go – examines both staged and unstaged files for rename detection. So Visual Studio will report renames before core git does. However, they should show the same results in status when you stage those changes.)

    Git Baby is a git and github fan, let's start git clone.