4 ms·
Yeah, you can re-run it, but then you have to merge the code. It's often not too bad, but can be tedious and complicated to figure out the first time around. W
by czue 3y ago
Yeah, you can re-run it, but then you have to merge the code. It's often not too bad, but can be tedious and complicated to figure out the first time around.
What I recommend people do is immediately commit the "clean" generated project to a new branch. Then you can apply an upgrade directly onto that branch, so it only has the "pure" diff. Then you can merge that to your main branch.
There's more info here, and a video walkthrough if you're curious: https://docs.saaspegasus.com/upgrading.html#using-branches-recommended https://docs.saaspegasus.com/upgrading.html#using-branches-r...
I've dreamed of automating it more, but would have to build an entire github integration to manage other people's compiled projects...
- RangerScience 3y agoHave you ever looked into Rails generators? They’re meant to be run over the lifetime of the project, and many libraries (specifically thinking of Devise, since it’s a large feature) have “install me” generators.
- noworriesnate 3y agoInteresting, thanks for the tip! I think what grandparent may have been referring to is if you run a generator with one set of arguments, make changes to the generated code, then you want to rerun the generator to regenerate the code with a different set of arguments. For example if you have a generator that has an argument for which logging library to use, you might want to change the logging library later. Maybe a bad example. I think this is where LLMs can thrive. Has anyone investigated using LLMs for resolving merge conflicts?