Changes between Version 24 and Version 25 of faq/gitification


Ignore:
Timestamp:
May 28, 2012, 6:53:22 PM (7 years ago)
Author:
Bart
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • faq/gitification

    v24 v25  
    258258=== Outline of git_subtree ===
    259259
    260 One way to solve the problem would be a Drupal module which clones the git repository of each Drupal module locally (and probably caches the data), determines the version information by using the ''git-subtree-split'' line returned by [http://git-scm.com/docs/git-log git-log] and writes this information to a ''.gitinfo'' file. A hook_system_info_alter could then retrieve this information and induce it into the local Drupal ecosystem. By adding ''*.gitinfo'' to ''.gitignore'' we could be sure that these files do not cause problems with upstream changes of the modules' git repositories.
     260One way to solve the problem would be a Drupal module which uses the [http://api.drush.ws/api/drush/docs!drush.api.php/5.x Drush api] to clone the git repository of each Drupal module locally, determines the version information by using the ''git-subtree-split'' line returned by [http://git-scm.com/docs/git-log git-log] and writes this information to a ''.gitinfo'' file. A [http://api.drupal.org/api/drupal/developer!hooks!core.php/function/hook_system_info_alter/6 hook_system_info_alter] could then retrieve this information and induce it into the local Drupal ecosystem. By adding ''*.gitinfo'' to [http://git-scm.com/book/en/Git-Basics-Recording-Changes-to-the-Repository .gitignore] we could be sure that these files do not cause any problems when syncing upstream repositories.