Automatic Project Updating |
Hi all! I have a new module to share that I'm pretty excited about. Been working on this one a long time, and there will be some more features to come but I wanted to get the initial version out...
Tatter\Patches Do you find it hard to keep all your project files consistent with the framework versions? Do you release libraries and modules that require developers to update their projects regularly? Let Patches help! Patches is a module for updating CodeIgniter 4 projects. It will analyze your project code against the vendor releases (current and updated) and help you patch files. Did you know that moving from version 4.0.2 to version 4.0.3 update 11 files in your project root? https://github.com/codeigniter4/framewor...2...v4.0.3 If you updated with Patches these would be handled for you! Easy to use 2-step process: 1. Install the module with Composer: Code: > composer require --dev tatter/patches 2. Use the CLI command to update: Code: > php spark selfupdate That's it! Visit the GitHub repo for more advanced configuration options, a play-by-play example of use, and the source code: https://github.com/tattersoftware/codeigniter4-patches https://packagist.org/packages/tatter/patches +++++++++++++++++++++++ As always your feedback is very welcome! Feel free to discuss here, or submit feature requests and bug reports over at Github. Thanks for reading!
Hi all! A quick note on Patches: I've just release version 2, which is such a big change it probably should have been its own library! To quote from my previous release notes:
Quote:`Patches` began as a concept for alleviating the very rote task of comparing framework revisions to their project equivalent. A tremendous amount of effort went into the handlers and interactive command, which amounted to the following:Version 2 is now launched, and I'm finding it to be a huge improvement. Check it out at https://packagist.org/packages/tatter/patches For those who prefer the current approach: version `1.2` will remain available (including a `1.x` branch), or check out Liaison Revision from our own @paulbalandan: https://github.com/paulbalandan/liaison-revision.
@b126 You need to merge "tatter/patches" branch, not "tatter/scratch".
(02-20-2023, 05:51 PM)kenjis Wrote: @b126 You need to merge "tatter/patches" branch, not "tatter/scratch". Unfortunately, I only see my master branch + the new tatter/scratch Is there a command to discover the tatter/patches branch? For info, I got no error when launching the patch command. Here below is an extract : Code: C:\wamp64\www\appgroup2>c:\wamp64\www\appgroup2\vendor\bin\patch And this is what I have with a git branch Code: C:\wamp64\www\appgroup2> git branch |
Welcome Guest, Not a member yet? Register Sign In |