You still need to copy and paste all this stuff into your_new_plugin.git and modify things to taste.
This precludes pulling in updates down the line from pamplejuce, which might be the antithesis of "best practice" (see: manual copy/paste).
Ideas:
Break all the github action "meat" out into its own official github action. This could be nice.
Provide a .cmake script to include as a submodule
Be at peace with providing an example (vs. a framework). Accept the fact that the CMake config will be copy and paste spaghetti, slightly different for each plugin.
The 🐘 in this repo is:
You still need to copy and paste all this stuff into
your_new_plugin.git
and modify things to taste.This precludes pulling in updates down the line from pamplejuce, which might be the antithesis of "best practice" (see: manual copy/paste).
Ideas: