So you work on a project which is version controlled and moreover it is version controlled by the almighty git himself. No matter whether you just got around all the teething problems and a steep learning curve of using git or you are a seasoned git professional – at one point or another you may find yourself in a situation where you want (or need) to:
No problem – you say? Sure – no problem as you can see if you follow the links above – nobody has ever got any problem with any of those operations. And no – using
$ git --follow
is not a solution either. Neither one knows when/where to try using some extra command line switches nor can one do it with non-command-line interfaces.. And no, unless you are a git geek, don’t even try to follow the discussions on those topics out there. The closest to something, which I felt could somehow work were a few discussions involving “filter-branch” command of git but God only knows what those dudes were really talking about. You know, this single big PITA alone can make one scream “GIVE ME MY SUBVERSION BACK!!!”
And you think there are no heroes anymore these days, don’t you? I tell you – There ARE! This awesome dude somehow made something out of this whole pile of conflicting, half-truth, semi-baked, scruffy-looking “advices” or just studied the matter on his own 😉 and came up with a shell script, which does the hardest part for you. I tried it. Sure I made a fresh pull to be up to date as action zero. Then backup of the whole directory first, then –dry-run second, then
$ git-mv-with-history myfile=mysubdirectory/
Rewrite cbb1a3111387949c0efde1540aa4565918f12f9b (1/117)
Rewrite ebb01ba7b2454a83f4e1b916384735a76cea15f9 (2/117)
Rewrite 18222fce98839724338fcdc833f3e307875eb6eb (115/117)
Rewrite 0b229d7fefa417f5b2e4975a87ea5ae69a2ebfe0 (116/117)
Rewrite e1ea07ce21b4a7ec6ba8e28dc1f5baba512bdbf2 (117/117)
Don’t forget the trailing slash if you want to move the file to a subdirectory or you may end up with your file being renamed into what you wanted a directory to be named!
I eyeballed all the files (checking them against the original clone of the repository) and the git status results..
silverdr$ git status
On branch master
Your branch and 'origin/master' have diverged,
and have 110 and 110 different commits each, respectively.
(use "git pull" to merge the remote branch into yours)
DON’T! DO! IT! I meant don’t “use git pull to merge the remote branch into yours”! Unless you want to ask for trouble, that is. Don’t try to simply push the changes either (but since your push will be most probably rejected anyway – it shouldn’t at least do much harm if you insist and try anyway). Now – what I did and it worked (but remember: YMMV!!) was:
silverdr$ git push --force origin master
Counting objects: 428, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (398/398), done.
Writing objects: 100% (409/409), 562.33 KiB | 0 bytes/s, done.
Total 409 (delta 154), reused 0 (delta 0)
+ e1ea07c...8879fe2 master -> master (forced update)
YES – there are still heroes. Even these days…