Version control for both Vagrant config and themes being developed [closed]

I have set up a local WordPress development environment using Chassis (based on Vagrant), this needed a bit of tweaking to get it how I like, so I feel like I should have this under version control. There will be changes in future.

I will be using this WordPress install for theme development, ideally I would like to develop in the “themes” folder, but would it cause problems having a Git repo within another Git repo?

Is there a way to manage this, keeping both the environment and theme under verison control?

1 Answer
1

I also asked this question on SO and the answer was to use .gitignore for the subfolders containing the themes I am developing. This has worked well for me.

Leave a Comment