You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is the original specification, but I realized that this might be a bit ambitious in a single shot, so we'll work on adding the ability to configure it in v2.
We need to discuss the final config schema but below is an early draft to start the ideation from
Draft Schemas
I am working on designing the config schema, and I wonder if it makes more sense to have two seperate plugins, one for issues only, and one for pulls only. Here I have a single plugin handling both, but perhaps the config can get a bit verbose and messy?
Heres a small example of a single (issue or pull) handler plugin config schema, which seems neat:
0x4007
changed the title
Generalized "GitHub Webhook + Contributor Role -> Rewards" With Config v2
Generalized "GitHub Webhook + Contributor Role -> Rewards" With Config v3
Sep 25, 2024
This is the original specification, but I realized that this might be a bit ambitious in a single shot, so we'll work on adding the ability to configure it in v2.
Builds upon #46, #48
We need to discuss the final config schema but below is an early draft to start the ideation from
Draft Schemas
Heres a small example of a single (issue or pull) handler plugin config schema, which seems neat:
Below is handling both
The text was updated successfully, but these errors were encountered: