Closed rndquu closed 3 months ago
I think it should be a separate (template) repository that contributors can fork and start with.
It should also support receiving payloads on GitHub actions (a built in backend upon forking) out of the box.
I never developed a plugin yet but I think include these instructions but then say that the developer can fork X repo for the plugin hello world template. That repo should bundle in a simple local server so they can fork and test locally as well.
I think it should be a separate (template) repository that contributors can fork and start with.
It should also support receiving payloads on GitHub actions (a built in backend upon forking) out of the box.
I agree with that but right now the whole kernel/plugin architecture is not clear and undocumented. This PR at least sheds some light on how kernel should work together with the plugins.
We do have a template for plugins, but the PR is not merged yet https://github.com/ubiquibot/plugin-template
Otherwise sure this can be useful for local testing I believe, fine by me too
This PR:
It feels natural (at least for me) to have a simple plugin ready for local testing right in the kernel instead of deploying https://github.com/ubiquibot/conversation-rewards or smth else which might be a tedious task.