The current project I’m working on for my new church website requires me to have a Git repository inside of another Git repository.  Typically when you do this, Git assumes you want to use a “feature” called submodules.  You probably don’t. I read up on submodules and don’t see any use case for them.  (There likely is one, of course, but this wasn’t it.)

It took a bit of searching, but if you add a “/” to the end of the folder that contains your nested repo when you are running  git add, you can fake the parent repo into acting how you’d expect, and not ignore everything inside.

Thanks to Felix from debuggable.com!

Share on FacebookTweet about this on TwitterShare on RedditShare on Google+Share on LinkedInEmail this to someonePrint this page