[wp-hackers] GitHub submodule theme development?
harry at dxw.com
Mon Jul 8 08:46:58 UTC 2013
Since we're having a git workflow discussion, here's ours :)
We make wp-content into a repo. For themes or plugins that are reused in
other projects, we add submodules that are shared. For things specific
to this project, they just live in the main wp-content repo, or
occasionally in their own submodule if that makes it easier to apply
Once we've got the wp-content directory set up we use Whippet to start a
local development server, and that takes care of the core files for us:
We also usually use Less for CSS, so the wp-content repo usually has a a
node manifest and a gruntfile so we can compile and minify css (and do
some other things) in the background while we're developing.
On 05/07/13 19:07, Micky Hulse wrote:
> I should mention, I'm wondering more about developing themes as Git submodules.
> Maybe I should be asking if anyone here uses symlinks for themes?
> Long story short, I'd like to have a separate version control process
> for themes within a version controlled WP install.
> My first thought was to use a Git submodule, but I have my concerns
> about being able to see the updates as I'm working locally (I've not
> used submodules too much, but I know they are a little bit more work
> to juggle).
> My second thought (which I had as I was going to bed) was to have a
> symlink in my WP theme's folder to another repository (locally) which
> contained my theme files. I did a quick bit of research last night,
> and I could not find anything specifically related to this technique,
> other than folks talking about how PHP/WP symlinks have drawbacks.
> Anyway, just wanted to clarify my question.
> It just feels a tad overkill to version control a whole WP install for
> the sake of theme development.
> What do you pro hackers do? :)
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers