This is common knowledge now but I’d like to make a post just so I can refer to it from other posts.\u00a0<\/p>\n
By default the Two things are needed in this case: (1) the working tree must\u00a0have some way of knowing where the Git repository is located, and (2) the Git repository must know where its working tree is.\u00a0<\/p>\n The easy way to do this is to The working directory “Test” only contains a file<\/span> called And if you go to that folder and check the config file you will see it points to the working directory (note the And this brings us to the non-easy way of separating the working tree from the repository.\u00a0If you have an existing repository, simply move the A neat thing about Useful stuff to\u00a0be aware of.\u00a0<\/p>\n","protected":false},"excerpt":{"rendered":" This is common knowledge now but I’d like to make a post just so I can refer to it from other posts.\u00a0 By default the .git folder – which is your Git repository – is stored in the same folder as your other files (the “working tree”). But it is possible to separate it from … Continue reading How to move\/ separate the .git folder out of your working tree<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false}}},"categories":[102],"tags":[103],"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/posts\/2283"}],"collection":[{"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/comments?post=2283"}],"version-history":[{"count":0,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/posts\/2283\/revisions"}],"wp:attachment":[{"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/media?parent=2283"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/categories?post=2283"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/tags?post=2283"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}.git<\/code> folder – which is your Git repository – is stored in the same folder as your other files (the “working tree”). But it is possible to separate it from the working tree if you so desire.\u00a0<\/p>\nclone<\/code> or init<\/code> a repository with the --separate-git-dir \/path\/to\/some\/dir<\/code> switch. For example:<\/p>\nC:\\Users\\Rakhesh\\Desktop>git init --separate-git-dir c:\\Users\\Rakhesh\\Code\\Test.git Test\r\nInitialized empty Git repository in c:\/Users\/Rakhesh\/Code\/Test.git\/<\/pre>\n
.git<\/code> (instead of a directory called .git<\/code>). This file contains a pointer to where the actual repository is.\u00a0<\/p>\nC:\\Users\\Rakhesh\\Desktop\\Test>dir\r\n Volume in drive C is WINDOWS\r\n Volume Serial Number is FA14-803C\r\n\r\n Directory of C:\\Users\\Rakhesh\\Desktop\\Test\r\n\r\n02\/19\/2015 02:35 PM <DIR> .\r\n02\/19\/2015 02:35 PM <DIR> ..\r\n02\/19\/2015 02:35 PM 39 .git\r\n 1 File(s) 39 bytes\r\n 2 Dir(s) 12,408,418,304 bytes free\r\n\r\nC:\\Users\\Rakhesh\\Desktop\\Test>more .git\r\ngitdir: c:\/Users\/Rakhesh\/Code\/Test.git<\/pre>\n
core.worktree<\/code> value):<\/p>\nC:\\Users\\Rakhesh\\Code\\Test.git>more config\r\n[core]\r\n repositoryformatversion = 0\r\n filemode = false\r\n bare = false\r\n logallrefupdates = true\r\n worktree = C:\/Users\/Rakhesh\/Desktop\/Test\r\n symlinks = false\r\n ignorecase = true\r\n hideDotFiles = dotGitOnly<\/pre>\n
.git<\/code> folder to wherever you want and add a .git<\/code> file as above and modify the config<\/code> file. And if you are cloning a repository, after cloning do as above. :)<\/p>\ngit init<\/code> is that you can run it with the --separate-git-dir<\/code> switch on an existing<\/em> working tree whose repository is within it, and it will move<\/a> the repository out to wherever you specify and do the linking:<\/p>\nC:\\Users\\Rakhesh\\Desktop>git init Test\r\nInitialized empty Git repository in C:\/Users\/Rakhesh\/Desktop\/Test\/.git\/\r\n\r\nC:\\Users\\Rakhesh\\Desktop>cd Test\r\n\r\nC:\\Users\\Rakhesh\\Desktop\\Test>dir .git\r\n Volume in drive C is WINDOWS\r\n Volume Serial Number is FA14-803C\r\n\r\n Directory of C:\\Users\\Rakhesh\\Desktop\\Test\\.git\r\n\r\n02\/19\/2015 02:45 PM 157 config\r\n02\/19\/2015 02:45 PM 73 description\r\n02\/19\/2015 02:45 PM 23 HEAD\r\n02\/19\/2015 02:45 PM <DIR> hooks\r\n02\/19\/2015 02:45 PM <DIR> info\r\n02\/19\/2015 02:45 PM <DIR> objects\r\n02\/19\/2015 02:45 PM <DIR> refs\r\n 3 File(s) 253 bytes\r\n 4 Dir(s) 12,406,550,528 bytes free\r\n\r\nC:\\Users\\Rakhesh\\Desktop\\Test>git init --separate-git-dir c:\\Users\\Rakhesh\\Code\\Test.git\r\nReinitialized existing Git repository in c:\/Users\/Rakhesh\/Code\/Test.git\/\r\n\r\nC:\\Users\\Rakhesh\\Desktop\\Test>dir\r\n Volume in drive C is WINDOWS\r\n Volume Serial Number is FA14-803C\r\n\r\n Directory of C:\\Users\\Rakhesh\\Desktop\\Test\r\n\r\n02\/19\/2015 02:45 PM <DIR> .\r\n02\/19\/2015 02:45 PM <DIR> ..\r\n02\/19\/2015 02:45 PM 39 .git\r\n 1 File(s) 39 bytes\r\n 2 Dir(s) 12,406,550,528 bytes free<\/pre>\n