Normally drupal.org inserts version information when a project is packaged. Git repositories do not contain this information. Git Deploy hooks into the Drupal update system and attempts to provide the version of modules and themes checked out of git.
Jochen Lillich von Freistil Consulting pflegt ein zentrales Drupal Git Repository auf das Jedermann lesend zugreifen kann. In diesem Git Repository sind nicht nur drei verschiedene Versionen des Drupal Core enthalten (Drupal Standard, Pressflow, Cocomore), sondern auch jeweils eine Version mit einem vorbereiteten Modulset. Enthalten sind gute 50 Module, die auf den meisten Seiten zum Einsatz kommen.
drupal settings per features speichern
collection of scripts to facilitate easy interoperation between a local git workflow and drupal contrib CVS
The git_drush module currently provides a Git core API layer for Drush modules that use Git functionality and some Git deployment commands we are developing for our own organizational deployment needs, that utilize Git submodules. I am thinking that the Git deployment commands will probably get separated in the future into a git_drush_deploy? (not sure on the name) module. So basically there would be a Git API module with no Drush commands, and the Git deployment module that used the API module.
Question arises: how to upgrade your Drupal installations * timely, * safely, * with confidence that none of your local customizations are lost; * without need to remember each line that was edited and re-applying those edits to new version; * without need to drastically change your workflow (very little discipline is needed actually); We show that Git solves those problems easily.
Drupal 6 with german translation and YAML templates and own modifications
