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-r...
I've dreamed of automating it more, but would have to build an entire github integration to manage other people's compiled projects...
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?
Pulling all of that down into a module that is managed and versioned allows you to upgrade your users. I now consider that almost table stakes for anything I build/manage as a platform team.
If you didn't think you needed the billing module when you ran it but later you find that you need it, the generator is of little use. You end up running it again to create a new project and manually copying in the billing pieces.
Or, if the generator is upgraded after you used it, it's to late for you.
I wonder if this tool tries to mitigate those issues at all.