You are here

README.txt in PatchInfo 8.2

Same filename in this branch
  1. 8.2 README.txt
  2. 8.2 modules/patchinfo_drupalorg/README.txt
Same filename and directory in other branches
  1. 8 README.txt
  2. 7 README.txt
CONTENTS OF THIS FILE
---------------------

 * Introduction
 * Requirements
 * Recommended modules
 * Installation
 * Configuration
 * Maintainers


INTRODUCTION
------------

The Patch Info module allows you to track information about patches in modules
or themes. It will show the information prominently in the update report and on
the update manager form.

 * For a full description of the module, visit the project page:
   https://www.drupal.org/project/patchinfo

 * To submit bug reports and feature suggestions, or to track changes:
   https://www.drupal.org/project/issues/patchinfo


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

This module does not depend on any other modules.


RECOMMENDED MODULES
-------------------

 * Drush (https://github.com/drush-ops/drush):
   When enabled, you can use drush patchinfo-list to get a list of
   patches applied to Drupal core or contributed modules on your system.
   Refer to drush help patchinfo-list for a list of available options.


INSTALLATION
------------

 * Install as you would normally install a contributed Drupal module. See:
   https://www.drupal.org/documentation/install/modules-themes/modules-8
   for further information.


CONFIGURATION
-------------

 * Choose one or multiple patch information sources.

   In 7.x and 8.x-1.x, all patches were tracked by adding information to
   *.info.yml files. Since 8.x-2.x, PatchInfo supports patch source plugins,
   that will be used to get patch information for your themes and modules.

   Two patch sources ship as submodules of PatchInfo. The 'info.yml' patch
   source gets patch information from '*.info.yml' files and the 'composer.json'
   patch source gets patch information from 'composer.json' files. See below
   for more information on how these patch sources work.

   You can use any number of patch sources at the same time. Just enable the
   submodule(s) that provide the patch source(s) you want to use or write a
   custom module that provides your own patch source plugin.

   The 'info.yml' patch source is fully compatible with patch information added
   using PatchInfo 8.x-1.x.

 * Add information about a patch using info.yml patch source

   In the *.info.yml file of a patched theme or module, add a new list like the
   one shown below:

   patches:
     - 'https://www.drupal.org/node/1739718 Issue 1739718, Patch #32'

   You can add multiple entries to the list. Each entry should start with the
   URL of the issue or patch followed by any kind of information about the
   patch. The URL is optional.

   You can use any URL or description, that is convenient to you.

   If you are patching a submodule, you may add the patch entry to the
   *.info.yml file of the submodule.

 * Add information about a patch using composer.json patch source

   The composer.json patch source assumes, that 'cweagans/composer-patches' is
   used for patch management. See https://github.com/cweagans/composer-patches
   for more information.

   For Drupal Core, it will check for a composer.json in your Drupal root
   directory or in the 'core' folder.

   Presently, the source plugin will skip any patches for packages outside the
   'drupal/' namespace.

 * Exclude module from update check

   The module will extend the update report settings form at Reports »
   Available Updates » Settings with a textarea, where you can list
   modules, that should be excluded from the update check. List one
   module per line. Use the machine readable module name of the module.
   Modules, which are excluded from the update check will be displayed
   prominently above the update report.

 * Write your own patch source plugin

   If you want to write your own custom patch source plugin, look at the
   existing submodules that provide patch source plugins for good examples.


MAINTAINERS
-----------

Current maintainers:
 * Patrick Fey (feyp) - https://drupal.org/u/feyp
 * David Franke (mirroar) - https://drupal.org/u/mirroar

This project has been partly sponsored by:
 * werk21 GmbH
   werk21 is a full service agency from Berlin, Germany, for politics,
   government, organizations and NGOs. Together with its customers,
   werk21 has realized over 60 Drupal web sites (since version 5).
   Visit https://www.werk21.de for more information.

File

README.txt
View source
  1. CONTENTS OF THIS FILE
  2. ---------------------
  3. * Introduction
  4. * Requirements
  5. * Recommended modules
  6. * Installation
  7. * Configuration
  8. * Maintainers
  9. INTRODUCTION
  10. ------------
  11. The Patch Info module allows you to track information about patches in modules
  12. or themes. It will show the information prominently in the update report and on
  13. the update manager form.
  14. * For a full description of the module, visit the project page:
  15. https://www.drupal.org/project/patchinfo
  16. * To submit bug reports and feature suggestions, or to track changes:
  17. https://www.drupal.org/project/issues/patchinfo
  18. REQUIREMENTS
  19. ------------
  20. This module does not depend on any other modules.
  21. RECOMMENDED MODULES
  22. -------------------
  23. * Drush (https://github.com/drush-ops/drush):
  24. When enabled, you can use drush patchinfo-list to get a list of
  25. patches applied to Drupal core or contributed modules on your system.
  26. Refer to drush help patchinfo-list for a list of available options.
  27. INSTALLATION
  28. ------------
  29. * Install as you would normally install a contributed Drupal module. See:
  30. https://www.drupal.org/documentation/install/modules-themes/modules-8
  31. for further information.
  32. CONFIGURATION
  33. -------------
  34. * Choose one or multiple patch information sources.
  35. In 7.x and 8.x-1.x, all patches were tracked by adding information to
  36. *.info.yml files. Since 8.x-2.x, PatchInfo supports patch source plugins,
  37. that will be used to get patch information for your themes and modules.
  38. Two patch sources ship as submodules of PatchInfo. The 'info.yml' patch
  39. source gets patch information from '*.info.yml' files and the 'composer.json'
  40. patch source gets patch information from 'composer.json' files. See below
  41. for more information on how these patch sources work.
  42. You can use any number of patch sources at the same time. Just enable the
  43. submodule(s) that provide the patch source(s) you want to use or write a
  44. custom module that provides your own patch source plugin.
  45. The 'info.yml' patch source is fully compatible with patch information added
  46. using PatchInfo 8.x-1.x.
  47. * Add information about a patch using info.yml patch source
  48. In the *.info.yml file of a patched theme or module, add a new list like the
  49. one shown below:
  50. patches:
  51. - 'https://www.drupal.org/node/1739718 Issue 1739718, Patch #32'
  52. You can add multiple entries to the list. Each entry should start with the
  53. URL of the issue or patch followed by any kind of information about the
  54. patch. The URL is optional.
  55. You can use any URL or description, that is convenient to you.
  56. If you are patching a submodule, you may add the patch entry to the
  57. *.info.yml file of the submodule.
  58. * Add information about a patch using composer.json patch source
  59. The composer.json patch source assumes, that 'cweagans/composer-patches' is
  60. used for patch management. See https://github.com/cweagans/composer-patches
  61. for more information.
  62. For Drupal Core, it will check for a composer.json in your Drupal root
  63. directory or in the 'core' folder.
  64. Presently, the source plugin will skip any patches for packages outside the
  65. 'drupal/' namespace.
  66. * Exclude module from update check
  67. The module will extend the update report settings form at Reports »
  68. Available Updates » Settings with a textarea, where you can list
  69. modules, that should be excluded from the update check. List one
  70. module per line. Use the machine readable module name of the module.
  71. Modules, which are excluded from the update check will be displayed
  72. prominently above the update report.
  73. * Write your own patch source plugin
  74. If you want to write your own custom patch source plugin, look at the
  75. existing submodules that provide patch source plugins for good examples.
  76. MAINTAINERS
  77. -----------
  78. Current maintainers:
  79. * Patrick Fey (feyp) - https://drupal.org/u/feyp
  80. * David Franke (mirroar) - https://drupal.org/u/mirroar
  81. This project has been partly sponsored by:
  82. * werk21 GmbH
  83. werk21 is a full service agency from Berlin, Germany, for politics,
  84. government, organizations and NGOs. Together with its customers,
  85. werk21 has realized over 60 Drupal web sites (since version 5).
  86. Visit https://www.werk21.de for more information.