Something in my chain is too complex, methinks...
I currently have a live site running off SVN, deployed with
I thought git could help me manage an open source branch, so that I
can make changes, and at will merge them into my open source and my
production branches (which i would then git-svn dcommit to svn and
deploy as usual).
The problem is that I can't find a way to 'desanitize' my open source
branch so that it is available to the public without the various
config files. In other words, a shallow copy that doesn't contain the
SVN history and loads of private config. I've read that one CAN make a
shallow git clone but actually, you can't then push this clone. Is
Do you recommend that i delete my production config, commit to svn,
svn export, git init, create open source and production branches, then
re-add the config on my production branch, then git-svn dcommit to
deploy? That sounds like it may be the only actual route, but seems
excessive. I guess I could actually abandon SVN completely....somehow
I thought I may be missing an option here...