What is the best git workflow for web developers who use cms? Let me explain the situation. In our last project, we switched to git for version control.
First we tried distributed version control, where each member had each own git repository and pushed / pulled it onto a bare repo. However, since we used Drupal (but Druapl is not the only CMS that does this), we relied on modules. When creating a page layout, Drupal (module) will create its own HTML code, which is sent to DB.
The SO problem occurs when we push the source code of a template to a naked repo, another developer can pull it out, but the db changes remain in the local db. At some point, we abandoned this style of workflow and started working on the same sigle server.
And in the next project, we just started working on one server and tried to create the maximum possible number of templates so that these templates move the modules, trying to create our own HTML code that will be sent to DB. But my question is: did any of you have this problem and how did you solve it?
This problem seems to be specific to web development simply because of the database.
I think this question is general and not specific to git or Druapl, it is rather a version control process with a cms problem.