Can a plugin depend on this repo?

[sudara]

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:

1. Break all the github action "meat" out into its own official github action. This could be nice.
2. Provide a .cmake script to include as a submodule
3. 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.

[sudara]

1. It's not possible to share "workflow templates" except intra-organization on github.
2. I'm not sure the cmake config will change enough to warrant modularization infrastructure
3. Github provides template repositories — maybe this is good enough for now.

Closing for now.