How do I develop a theme with multiple devs (GiHub Workflow)

  • I would like to develop a WordPress theme with another person: As far as I understand it we could use GitHub for version controlling but what’s about the SQL database? Cloning and pushing the WordPress theme folder shouldn’t be a problem but how do I synch the database?

    The only solution I found is from a post which is 10 years old (and maybe outdated?). It says that you could import/export the database manually with a plugin every time you clone the theme folder. But this doesn’t seem to be very efficient for me. Having a remote database is another solution according to the post…

    So my question is: What do other developers do to synch the database across multiple local workstations when working on a wordpress theme together?

Viewing 1 replies (of 1 total)
  • Moderator bcworkz

    (@bcworkz)

    We have standard content that is intended to thoroughly test a theme’s CSS. That’s the extent of our DB content. If anyone needs additional content for the specific feature they are working on, they generally keep it to themselves, no one else is working on that specific component. If a component’s content needs more than one dev, they can export/import among themselves.

    In the end, when it comes to alpha/beta testing, the additional content from various devs could be merged into the common DB.

    May not be the best system, but it’s what we do. Themes shouldn’t be dependent on any specific content, so not having the exact same DB available is not a problem..

Viewing 1 replies (of 1 total)
  • The topic ‘How do I develop a theme with multiple devs (GiHub Workflow)’ is closed to new replies.