I recently ran into an issue on one of our projects with a Git repository that stumped me for a few days. It was a small project: only three developers committing to a single repository hosted on Pantheon. I kept on running into an issue where I (or any of the other developers) could ever get my local repository to a “clean” state.

Git’s a ripper Version Control System, and considering its growing adoption, you can’t afford to be a drongo when it comes to leveraging it. No worries though, just head on over to Sydney the day before DrupalCon kicks off, take DrupalEasy’s action-packed Blue Collar Git training, and Bob’s yer uncle! 

The Yank (that’d be me) from DrupalEasy is putting on this fast-paced workshop that’ll help you master Git and get gobsmacked at how much more effective you get as a Drupal developer, themer or project manager. 

Using Git to move the code base of a Drupal site from a local development environment to a hosting provider (or vice-versa) is a necessary skill that most Drupal site builders should have. Configuring and utilizing a remote Git repository can be an especially daunting task for people who don't have a strong background with version control systems. 

Great feedback from my "Tinkertoy Git" Tampa meetup and DrupalCamp Nashville presentation has inspired me to make it bigger. Much bigger. The expanded full-day "Blue Collar Git" workshop covers not only the basics of the distributed version control system, but also delves into remote repositories, resolving conflicts, and working with patches.

Let's face it - anyone with anything more than a passing interest in the Drupal community is probably aware that we're in the midst of embracing Git, "the fast version control system". As with just about everything else in our community, we are continuously jettising outdated technology and replacing it with modern solutions.