I like this module, the cataloging features make sense but patching sites on production isn't going to happen much, plus Drush users prefer the command line to apply patches, but I see a happy middle this module can provide. Since patches are sometimes lost or forgotten, keeping a list of patches in the database helps keep them "remembered" and portable.

My suggestion is to add an export UI that provides a simple textarea that combines the various patches into a `patches.make` file described here: https://dev.acquia.com/blog/patching-drush-make

Then Drush users can easily generate the `patches.make` file from any db archive, and technically disable the module/UI when not used if that's their preference.

Comments

Chris Charlton created an issue.