Git

Since the release of Drupal 8 in November 2015, developers and site maintainers have been coming to terms with the configuration management that is now a big part of how we support Drupal 8 sites. I took some time to learn the strategies different developers have adopted to make configuration management work for them. In reviewing the material found online, I noticed a definite progression in these strategies from the release of Drupal 8 to the time of writing this nearly two years later.

In the first article of this series we talked about the Drupal 8 Core approach to configuration management, how it helps us, and how it can present certain challenges in our site support and development work.

As a veteran web developer of nearly 20 years, one of the more difficult things I ran into when I started with Mediacurrent, a Drupal agency, was working within the constraints of a version control system.

Company X has a problem. Their distributed team of developers are constantly introducing regressions into production with no clear point for QA to become involved and without a Git guru on the team, they are wasting time untangling commit conflicts. If this sounds like your team, then “git-flow” may be the solution.

You've hopefully been using Git for a while now, but what happens when you have a multiple environment setup, numerous team members working on the same project and code breaking on production while new code is being worked on? Git-flow is here to save the day. In this webinar I'll take you through a daily use of git-flow including concepts behind git-flow and how to apply them in your day-to-day work.

Have more questions? Ask them in the comments below or come see this presentation in person at DrupalCamp Florida on April 20.