Apologies if this seems like a stupid or obvious question, but here goes...
How do most plugin developers structure their local git repositories so they can a) develop plugins locally and b) publish to GitHub?
I had initially set up a git repo within my /Library/Application Support/.../Sketch/Plugins folder, where changes to code can be executed immediately by Sketch. If I broke anything while working, I could revert or switch back to the master branch with ease.
But for publishing to GitHub I need a repo that contains the .sketchplugin container as well as a README and appcast.xml. I'd ideally like to manage that with git too, but I can't put that repo in /Library/Application Support/.../Sketch/Plugins as there are lots of other plugins in there.
Should I set up a git repo for the main plugin (containing the .sketchplugin, the README and appcast.xml) and then add a submodule for the /Contents/Sketch folder, which uses the "working" Sketch folder under Application Support as its origin? Or is there a simpler way of doing it?