I never liked the git bare repository approach, because it's each to accidentally add files to it that you don't intend (if you forget to run git init in a new

I never liked the git bare repository approach, because it's each to accidentally add files to it that you don't intend (if you forget to run git init in a new project directory; or if some code generator decides to "re-use" your existing git repository). I prefer the symlinks approach, but I never liked how all of the symlinks managers tend to leave broken symlinks all over the place. That's why I created my own solution, which maintains a state file in the repo, so doing something like deleting a config file or switching a git branch doesn't result in a bunch of broken symlinks lying in your system. https://github.com/cgamesplay/dfm https://github.com/cgamesplay/dfm