I've been reading up and trying out various workflows with Wordpress/git. There's a number of options available and I've got a few workflows roughly modelled but no matter which one I choose there's always someone or something that'll lose out.Workflow adoptersDevelopers (competent, used to git)Designers (not used to git, but competent)CMS users (less competent)SetupThis part isn't really subject to change unless a workflow is really, really worth it. Production server pulls from prod/master branchIn house development server pulls latest from develop branchUnit tests are available that should be run before local push to serverWhen develop receives a push and there's a new tag, automated tests run on the Dev server. If they pass, merge with productionOption AAll files stored in gitDatabase schema & content stored in gituse of local-config.php files for easy local deploymentdisallow access to admin panel for live site on production and development serverProsall work done locallyeasy to redeployeverything is controlled by git for traceabilityknown working version (no auto updates to mess things up potentially)Consminor edits to posts/pages have to be done via source control each timenon-devs may end up using this system moremerging a raw SQL file is problematicOption BAll files stored in gitDatabase schema & content stored in gituse of local-config.php files for easy local deploymentdisallow access to admin panel for live site on production onlyProsmostly the same as Option A but changes to posts/content can now be done via Dev servereasier for less technical folks to understandchanges to Dev site db checked in by the server automatically every so oftenConslosing traceability with commits as it'll just be a user server that committed a page content changeopening up potential to have people working on Dev server and skipping localpain to manageOption Conly templates/custom plugins stored in gitdb backed up by other method (probably manually)posts, pages, plugin installs, updates can be done live on the prod site (yuck)Prosmost user friendly Consleast Dev friendly. not quick and easy to redeployno idea if update to core breaks a testno idea if an update to a plugin breaks stuffusers editing pages on the fly liveIs there any good happy medium or better way of working that I'm totally missing or is it a suck it and see job where we have to implement it, find the issues folks are having and fix those. 
Suitable workflow for multiple people with multiple skill levels
workflows