You are here

Home » API reference » Git Deploy 6.2

README.txt in Git Deploy 6.2

Same filename and directory in other branches
  1. 8.2 README.txt
  2. 6 README.txt
  3. 7.2 README.txt
  4. 7 README.txt
INTRODUCTION
------------

Git Deploy lets you develop on a live site and still satisfy version
requirements and get accurate results from the update status system. This makes
it easier to contribute to the projects you use.

Version information is added automatically when the Drupal packaging system
creates a release. If you check out a contributed project from the Drupal
repository with Git, it should not have any version information. Git Deploy gets
the missing version information from the project's Git log.

* Project page: https://www.drupal.org/project/git_deploy
* Issue queue: https://www.drupal.org/project/issues/git_deploy


REQUIREMENTS
------------

* Access to the git command.
* The ability for PHP to execute shell commands.
* To get accurate update status information, enable the myDropWizard module
  (https://www.drupal.org/project/mydropwizard).


ALTERNATIVES
------------

A project’s dev release changes whenever a maintainer updates its branch. To
enforce consistency among sites using a dev release, you can lock them to the
same release by checking out a specific Git commit. You would not contribute
changes from these sites back to the project. Drush 8
(https://docs.drush.org/en/8.x/) can automatically add version information to
projects you check out with Git.

* The drush pm-download command with options --package-handler=git_drupalorg
  --gitinfofile performs a Git clone and checkout and adds version information
  to the project info file.
* The drush make command automatically adds version information to the project
  info file without additional options.

Composer Deploy (https://www.drupal.org/project/composer_deploy) gets version
information from Composer metadata for projects installed with Composer.

File

README.txt
View source 
  1. INTRODUCTION

  2. ------------

  3. 

  4. Git Deploy lets you develop on a live site and still satisfy version

  5. requirements and get accurate results from the update status system. This makes

  6. it easier to contribute to the projects you use.

  7. 

  8. Version information is added automatically when the Drupal packaging system

  9. creates a release. If you check out a contributed project from the Drupal

  10. repository with Git, it should not have any version information. Git Deploy gets

  11. the missing version information from the project's Git log.

  12. 

  13. * Project page: https://www.drupal.org/project/git_deploy

  14. * Issue queue: https://www.drupal.org/project/issues/git_deploy

  15. 

  16. 

  17. REQUIREMENTS

  18. ------------

  19. 

  20. * Access to the git command.

  21. * The ability for PHP to execute shell commands.

  22. * To get accurate update status information, enable the myDropWizard module

  23.   (https://www.drupal.org/project/mydropwizard).

  24. 

  25. 

  26. ALTERNATIVES

  27. ------------

  28. 

  29. A project’s dev release changes whenever a maintainer updates its branch. To

  30. enforce consistency among sites using a dev release, you can lock them to the

  31. same release by checking out a specific Git commit. You would not contribute

  32. changes from these sites back to the project. Drush 8

  33. (https://docs.drush.org/en/8.x/) can automatically add version information to

  34. projects you check out with Git.

  35. 

  36. * The drush pm-download command with options --package-handler=git_drupalorg

  37.   --gitinfofile performs a Git clone and checkout and adds version information

  38.   to the project info file.

  39. * The drush make command automatically adds version information to the project

  40.   info file without additional options.

  41. 

  42. Composer Deploy (https://www.drupal.org/project/composer_deploy) gets version

  43. information from Composer metadata for projects installed with Composer.